In Agile project management, we must prioritize a requirements list for release planning, iteration planning and the insertion of new requirements. But there are several techniques to do this.
One of the most popular methods of prioritizing Agile project requirements is the "MoSCoW" approach. This stands for 'Must, Should, Could, Won't.' The only problem with this method is that everything is usually a must -- which doesn't allow proper Agile release planning because the requirements aren't necessarily put in order of priority.
Another method is the Kano model, developed by Professor Noriaki Kano, which strives to fulfill requirements and please customers. This model features four components:
â€¢ Must haves are elements the product cannot ship without.
â€¢ Dissatisfiers are things the product must NOT include.
â€¢ Satisfiers include requirements where the more you have the better the product is perceived. Like a marketing checklist, each feature adds incremental value.
â€¢ Delighters take the product beyond simply meeting the requirements to boosting customer satisfaction and recommendation.
Several prioritization models put together a table weighted by two variables: features and customers. Each feature is weighted by its value to each customer. The sum of the weights multiplied by the scores makes it possible to see which features are most useful overall across the set of demanding customers.
No matter which technique is used, your list of project requirements must be sorted from most to least valuable.
What techniques do you use to prioritize requirements?