Agile Zone is brought to you in partnership with:

Seasoned software Architect, a passionate Agile, Lean Practitioner and a successful trainer. Always inspired by innovative ideas and human behavior/psychology. Trying to find a balance between pragmatism and purity. Venkatesh is a DZone MVB and is not an employee of DZone and has posted 45 posts at DZone. You can read more from them at their website. View Full User Profile

6 Backlog Prioritization Techniques

  • submit to reddit

imageThere are several ways to prioritize the requirements in the backlog. Some of the most popular ones include,


imageM - MUST have this.
S - SHOULD have this if at all possible.
C - COULD have this if it does not effect anything else.
W - WON'T have this time but would like in the future.

Each requirement will have the priority which would be tagged to MSCW. “M” being the highest and “W” being the lowest.

This site gives a very good explanation about this technique.

Business Value Based

image In this case, each requirement carries a business value it could potentially generate to the company. The business value would be decided either by the Product Owner or the Product owner team.

The requirement with highest business value is implemented during earlier releases .

Technology Risk Based

image In this method, requirements are prioritized based on the risk associated in implementing it. The risk is typically based on the technology.

The requirement with highest technology risk is implemented during the earlier iterations.

Kano Model

imageIn this method, the requirements are prioritized based on the customer preferences.

  • Attractive
  • One-Dimensional
  • One-Dimensional
  • Must-Be
  • Indifferent
  • Reverse

You can read more details about this model here

Walking Skeleton

image In this method, the requirements are selected such that minimal carefully selected end to end features are built within a short span of time.

Validated Learning

    image In this method, features are chosen based on the highest market risk i.e. some thing that is not experimented yet. Release it to the market, get the feedback and apply the learning onto the new feature.

    This deck gives a good view about validated learning in the context of lean startup

Published at DZone with permission of Venkatesh Krishnamurthy, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)