Tag Archives: Mike Cohn

Prioritization – Part 2: MoSCoW and Risk-Value

As introduced in the first blog, prioritization is difficult.  The first and most important question is “should we do this at all?”  Once you determine that an effort is worth doing, we have to figure out where it falls relative to the other things in the queue.  There are a number of tools that we can use in this effort.

MoSCoW

The first tool in our arsenal is from Dynamic System Development Method (DSDM) and it is an acronym for Must have, Should have, Could moscow_blog2have, Want.  The technical definition for each category is as follows:

Must have: all features classified in this group must be implemented, and if they are not delivered, the system would simply not work.

Should have: features of this priority are important but can be omitted if time or resources constraints appear.

Could have: these features enhance the system with greater functionality, but the timeliness of their delivery is not critical.

Want to have: these features serve only a limited group of users and do not drive the same amount of business value as the preceding items.

To put MoSCoW  in action, we pull a reference from our book, Introduction to Agile Methods.  In this example, we are looking at the payment methods that could be offered on a new eCommerce site.

Must have: ability to accept Mastercard and Visa

Should have: add American Express and Discover

Could have: add ACH payments for transactions directly through banking institutions

Want to have: add gift cards

By understanding where each feature falls relative to the MoSCoW parameters, the prioritization is much easier.

Agile Book – Technical Debt

In the next edition of this blog series highlighting excerpts from our upcoming book, we will tackle the tricky subject of Technical Debt.  To be honest, I had a hard time choosing a single topic from this chapter because there are so many great topics covered – debt2Definition of Done, Planning Poker, Value Stream Mapping, the Kano Model, Velocity, the XP Planning Game – and much more in this chapter on Grooming and Planning.  And it includes an interview with none other than Mike Cohn!  If this post, or any of the previous ones on Roles or Requirements or our guest blog from co-author Sondra Ashmore inspire you to want to purchase the book, please visit Amazon and search on Introduction to Agile Methods.

Back to Planning and Grooming, here are the Learning Objectives for the chapter.

Learning Objectives

  • Understand the elements of a product backlog and what traits lead to the strongest deliverables
  • Dive into prioritization and learn different methods for understanding what is the most important feature or item to work on
  • Explore estimation and the different practices and measures that are used today
  • Understand story points and planning poker as ways to discern the level of effort and complexity of the user stories/requirements
  • Learn the other inputs that affect the planning process, such as team velocity, definition of “done,” technical debt, and bugs/defects
  • Evaluate Sprint planning and the XP planning game to learn how commitments are made and work is planned
  • See how maintenance work can be incorporated into Agile teams
  • Review the triple constraints model and how it is handled within the Agile framework