Building a Better Product Backlog

1,342 views
1,251 views

Published on

In a smaller organization, different people need different product information. Sales wants a longer term roadmap, development wants to see what's next in the backlog and management wants to see why items are being prioritized the way they are. Here's a technique from my Lean 2011 talk on visibility.

Published in: Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,342
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
9
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Building a Better Product Backlog

  1. 1. Nowhere to Run, Nothing to Hide Nothing to Hide Making Your Organization Progress and Agile Transition Visible Presented at Lean 2011 by Jason Little http://www.agilecoach.ca
  2. 2. a better backlog Jan Feb Mar Theme 1 - cost of delay* Theme 2 -cost of delay* Theme 3 - cost of delay* Theme 4 - cost of delay* Sprint 1 - feature a - fix b - fix c Sprint 2 - fix f - improvement g - fix h Sprint 3 not sure yet story/epic current story/epic story/epic story/epic story/epic story/epic story/epic story/epic story/epic story/epic Release
  3. 4. A Better Backlog <ul><li>prioritizes themes </li></ul><ul><li>makes visible what’s going on with the product </li></ul><ul><li>shows current sprint team commitment </li></ul><ul><li>loosely plans future sprints based on velocity </li></ul>more visible charts and examples at http://www.agilecoach.ca/visibility *see Jeff Anderson’s post about cost of delay at http://agileconsulting.blogspot.com

×