Wednesday 26 August 2009

Help for Product Owners: Prioritizing the backlog

First Things First: Prioritizing Requirements

Karl Wiegers provides some advice on the topic of prioritizing the backlog and he throws in a spreadsheet for free as well:
"Customers are never thrilled to find out they can’t get all the features they want in release 1.0 of a new software product (at least, not if they want the features to work). However, if the development team cannot deliver every requirement by the scheduled initial delivery date, the project stakeholders must agree on which subset to implement first. Any project with resource limitations has to establish the relative priorities of the requested features, use cases, or functional requirements. Prioritization helps the project manager resolve conflicts, plan for staged deliveries, and make the necessary trade-off decisions."
You can find his spreadsheet here.


Digg Technorati Delicious StumbleUpon Reddit BlinkList Furl Mixx Facebook Google Bookmark Yahoo

Google Analytics