The time has come where you think you need a project management tool. Your small team has grown or your projects are becoming numerous or large enough for you to need that extra organizational help.
But - and it's no small but - just by looking around you realize there is a plethora of such tools... And we're talking so many of them that even on page 2 of Google, right next to the dead body, there are still plenty of them. Free ones, not so free ones, complex ones, simple ones... And none of them exactly doing the trick for you - there is always that little feature missing that you really want.
Well - it's simple: they are not tools for developers. They are not meant to specifically help developers.
Of course you can make do, and as your team grows you will probably be provided with one of these tools anyways. But before that, let us show you how Keypup can provide you with the basics - on top of everything else it does (read here and here, it's pretty cool) - so that you don't get the one more system to handle.
How do we use Keypup project management features?
The Keypup platform automatically prioritises issues and pull requests assigned with a due date. That in itself provides you with all the visibility you need about your own work and current progress as well as the one of your colleagues.
At Keypup, we use Keypup. No wonder. But we also use it as a light project management tool in combination with Github.
We have weekly sprints.
We create weekly milestones on Github repositories for issues we schedule for the current sprint or the next one. And of course, we don't forget to assign someone to the issues!
Now each milestone is assigned and has a due date. When the due date is for next week - somewhere during our next sprint - it will automatically appear in our priority inbox from Monday, until it is achieved and closed.
The priority inbox helps us navigate all issues and tasks according to their criticality. As the sprint progresses and time goes by, items in the priority inbox will raise in priority and ranking, and you will be alerted by Keybot of course.
This way, we don't need to pull our hair trying to see where we start to achieve all the objectives of our sprint. We just let ourselves be guided by Keypup. And frankly, it's cool not to have to stress about the pipe of activities, but rather to follow guidance to just get it done!
When someone opens a pull request related to an issue, the team immediately assigns a reviewer and the weekly milestone to it. This ensures that the reviewer will automatically see the pull request appear in their priority inbox.
That's it! Easy weekly-based sprint planning without the need for any other tool.
Of course, your sprints can be bi-weekly. Or you may simply want to schedule items in the future and prepare a roadmap for each of the developers for the next while. Well, good news everyone! Keypup does that too.
By assigning milestones to issues in the future, these issues will automatically appear in the "coming up" tab of the priority inbox and when the time comes, closer to the due date or when their criticality raises, it will show up in the priority inbox as shown above.
Scheduling and assign items in the future is a good idea.
Because they will eventually appear in the priority inbox. At that time, you can decide to either implement them, or to reschedule them for later. But at least, important items or great ideas do not get buried and lost in the gigantic backlog sitting somewhere in your systems. You get to be gently nudged about them once and a while without effort.
What would be really neat is if you try the above and give us some feedback. We're here to help our fellow developers so any insight or comment you may have will be extremely useful. Don't hesitate to write us a line at firstname.lastname@example.org .