Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
1 of 4

Building a Better Product Backlog

1

Share

Download to read offline

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.

Related Books

Free with a 30 day trial from Scribd

See all

Related Audiobooks

Free with a 30 day trial from Scribd

See all

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

×