3 ways to prioritize your development items

A clean kitchen is easier to cook in, right? Your plates are organized, utensils are in the right place, everything you need is there to cook like a chef. 

Well, that’s exactly the same with your work, a clean setup is a good start to be productive.  

At Keypup we understand how crucial it is for a developer to be organized. Indeed, maintaining productivity and velocity is hard. Our mission is to optimize the SDLC and get rid of the little mess around pull requests and issues.

To do so, we’re here to give you pro tips about task prioritization. On Keypup, you now have three levels of prioritization to control your pull request flow. Amazing, right? Let’s explain those features and see how you can work to deploy faster with your team.

Wait, you don’t know about us yet? It’s okay, you’ll catch up here. Keypup helps thousands of developers to organize their daily work and code without all the pesky tasks surrounding development such as checking out your JIRA ten times a day or getting your email inbox flooded by notifications.

OK, let’s jump right in. 

3 ways to prioritize your development items


1. Two features, different views, same technology

Once you sign up to Keypup, you have the possibility to connect your usual repository and issue tools (GitHub, JIRA, Trello, Bitbucket, and more) along with the projects you’re involved with (of course, only project maintainers have the authorization to connect projects to Keypup).

The Priority Inbox and the Agile board fetch your repository data to automatically provide a sorted feed of your hottest priorities based on the review status, build status, mergeability check, due date, etc. 

We are developers ourselves, so when we submitted Keypup to early adopters to validate the idea, we knew this pull request-driven tool would be a good productivity tool because it’s designed especially for software developers and not project managers. And that changes everything.

So as mentioned earlier, you get offered two different views using the same data-driven technology. 

The Priority Inbox displays your data in a sorted feed with different levels of criticality, deadlines, and recommended actions. The good thing about Priority Inbox is that it’s your own safe place that shows everything you’re working on and what has to be done. 

What’s more, you can also nest your issues in related pull requests for better visibility. That way, you won’t miss anything, and you don’t have to jump between your apps to make sure you’re not missing any code review for instance.

The Priority Inbox

 

The Agile board has a different approach. As mentioned in the title, it’s more for Agile teams.

We found out that Agile has become a weapon used by the project manager to monitor projects, but Agile was never meant to be for them! We saw a lot of developers complaining. They claim to be bound to processes that make them waste hours of sprint meetings, filling JIRA tickets, not to mention retrospective meetings. 

So the Agile board is a visual of both the individual and the team’s progress, for developers only. Each column in the board is configured to retrieve issues and pull requests matching specific criteria. Plus a little bonus, the board is fully customizable. Whether you’re working on a Scrum or a Kanban project, you’re able to choose your work mode and see what the other’s tasks are.

3 prioritization levels - Priority Inbox
The Agile board


2. Prioritization rules: 

Because software developers have different missions and work in different sectors, we knew that we couldn’t find the perfect recipe working for every developer. So we brought a little customization feature in our Priority Inbox: Prioritization rules.

You can set matching filters to override the default priority settings we built. There are many reasons to use them, we have an example here of using prioritization rules to manage a side project. You also use them to create reminders, separate different groups of projects, etc. 

3 prioritization levels - PI rules
Learn more about prioritization rules 

3. Manual priorities assignment

Our latest feature gives you more freedom and control over your Priority Inbox. Sometimes, items do not belong to your feed (neither the main, the coming up, or the pending peer tabs). So If you just want to remove a specific pull request or an issue from your feed, easy! You can manually take action on each item.

Sometimes you just have the odd item that should be prioritized differently. No worries! You can now do it!
Manually override the priorities (even your custom ones) by selecting on the given pull request the priority mode.

3 prioritization levels - Manual priorities
Learn more about manual priorities assignments here.


See? We put a lot of effort into this because we desperately wanted to work more comfortably. And we know that thousands of software developers are on the same boat. So feel free to check out those different levels of prioritization and see which one is a good fit for your development needs.

There are a lot more features such as the Review and Merge, the Data Explorer, and the Retrospective tool. In this article, we focused here on prioritization, but we also cover different aspects of a typical daily work of a developer. Scroll our blog to see more!

You may also like reading: