Building a Better Product Backlog

by Jason Little on Apr 26, 2011

396 views

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.

Less

2 Embeds 135

http://www.agilecoach.ca	133
http://agilecoach.ca	2

Statistics

Favorites: 0
Downloads: 2
Comments: 0
Embed Views: 135
Views on SlideShare: 261
Total Views: 396

Building a Better Product Backlog — Presentation Transcript

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

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

A Better Backlog

prioritizes themes

makes visible what’s going on with the product

shows current sprint team commitment

loosely plans future sprints based on velocity

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

Building a Better Product Backlog

by Jason Little on Apr 26, 2011

Accessibility

Categories

Tags

Upload Details

Usage Rights

2 Embeds 135

Statistics

Building a Better Product Backlog — Presentation Transcript