During the product development process, you will have ideas, suggestions and bugs coming from left and right. That’s why you’ll need to prioritize tasks in your backlog and make sure that the most impactful ideas are developed first.
By doing task prioritization you will define what will go into the next sprint and what will be developed later - or what you won’t be working on at all.
So, how do you prioritize the backlog?
There are several backlog prioritization methods that can help you manage your backlog, and you can choose whichever works best for you. In this guide, we will cover one of the most popular methods, called the MoSCoW method.
The MoSCoW method is a prioritization technique that allows you to reach the common ground with all the stakeholders and make sure to deliver the most important requirements first. The system differentiates between these five levels of priority:
Mo (Must Have): The most vital product requirements that you (or your users) can’t live without.
S (Should Have): These requirements are important but not absolutely essential for your next release.
Co (Could Have): These requirements are nice to have, but not as important as Should Have items.
W (Won’t Have): User stories that provide little or no value so you can leave them for later.
Once you start prioritizing tasks in your backlog in such a way, it will become much clearer for you and all the stakeholders what should be worked on in the next sprint. To make this prioritization more visual, you can create separate labels for these four priority levels.
To make your product backlog even cleaner, you can create a separate folder for your W (Won’t Have) items. You can call the folder ‘Long Term,’ ‘Future Tasks,’ etc. In Infinity’s Product Development board, we call this folder ‘On Hold’ and we keep all the lower priority tasks there.
Of course, you should also revisit this folder from time to time, and check if some of these items have deserved their spot in the backlog or if they should be completely scratched from the list.
You don’t have to follow the MoSCoW method from A to Z. To make things simpler, you can create a label set in your Backlog folder called ‘Priority’ and give it values Mo - High, S - Medium, Co - Low and W - None. In this case, the items with no priority will go to the ‘On Hold’ folder, while the rest will become contenders for the sprint.
Here’s how you will prioritize your backlog in Infinity’s Product Management board:
To make sure you’re objectively prioritizing tasks, you’ll need to take into consideration a few other factors such as:
All of these factors will be crucial to help you decide which of the backlog items will go into the next sprint. Here’s why this is important - sometimes you will have a medium or low priority task which is low risk, low cost and super easy to implement.
In this case, you might consider adding this item to the sprint since it’s going to be an easy but nice-to-have addition to your next release.