Inevitably Agile

somethings are just inevitable …

Prioritization of the backlog

All items in a backlog MUST be prioritized. They cannot be of equal value πŸ™‚ The items at the top are seen as highest priority and those at the bottom, lowest. Once an item (story) is completed – it MUST be removed from the backlog (please see this post on keeping your backlog clean and relevant).

 

Everyone has their own way of prioritizing (not all are relevant to everyone) here are some factors to keep in mind:priorities1 Should Requirements be Prioritized?

(from http://www.agilejournal.com/articles/columns/column-articles/2647-grooming-the-product-backlog)

  • value
  • knowledge/uncertainty/risk
  • Releasability
  • dependencies

(from http://agilesoftwaredevelopment.com/blog/peterstev/prioritizing-product-backlog)

  • Minimum Marketable Feature Set – the first pass to narrow the list of stories
  • Business Value First – Focus on High Value Functions
  • Bang For the Buck – Go for easy wins
  • Technical Risk First – Do the hard things first
  • Defer Risk – Do the hard things later (or never)
  • Vote – Ask your users

 

Remember

Many POs only prioritize at a very high level (think larger than epic – items that would take 1 month or more). And once those are broken down – everything within that β€˜larger’ topic is given the same priority. This is a mistake. Not everything you think of for a large topic will be relevant to a release – some stories might be completely unimportant and thus left off the release totally. Remember to prioritise all stories according to value.

risk

If you are struggling, I like using a block diagram. Classify your story into one of the 4 blocks and then use the values in the cloud for priority order.

Another trick is to use MoSCoW:

M – MUST have this feature – the product will fail to meet needs without this 
S – SHOULD have this feature – an important feature that has an acceptable work around
C – COULD have this feature – wish list item
W – WON’T have this feature at this time – might move to Must, Could or Should in the future.

 

Must Reads:

http://agiletales.com/tag/prioritization/

http://www.agilepalooza.com/Boston09/slidedecks/patton_backlog_prioritization_agilepalooza_boston_09.pdf (presentation)

http://www.infoq.com/presentations/prioritizing-your-product-backlog-mike-cohn (video)

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: