Agile Day | Product Backlog Tips and Tricks | Roman Pichler
Upcoming SlideShare
Loading in...5
×
 

Agile Day | Product Backlog Tips and Tricks | Roman Pichler

on

  • 823 views

2011-11-01 | 10:40 AM - 11:40 AM | Victoria ...

2011-11-01 | 10:40 AM - 11:40 AM | Victoria
Many product backlogs I have come across are not managed very well: They either contain too much or too little information, ranging from literally a handful of user stories to many hundred items. This talk provides ten practical tips that help you to stay on top of it. The tips include making the product backlog DEEP, understanding what "ready" means, and how the backlog can be visualised.

Statistics

Views

Total Views
823
Views on SlideShare
823
Embed Views
0

Actions

Likes
0
Downloads
33
Comments
0

0 Embeds 0

No embeds

Accessibility

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Agile Day | Product Backlog Tips and Tricks | Roman Pichler Agile Day | Product Backlog Tips and Tricks | Roman Pichler Presentation Transcript

  • Product  Backlog  Tips  and  Tricks   JAX  London  2011   Roman  Pichler   @romanpichler   romanpichler.com  
  • Two  Common  Mistakes  ©  2011  Pichler  ConsulDng  Limited   2  
  • The  Product  Backlog   •  Contains  the  work  to  create  a  successful  product   •  This  includes   –  Features  and  requirements   –  Defects  and  maintenance  work   –  Prototyping  and  refactoring  work   Product  Backlog  ©  2011  Pichler  ConsulDng  Limited   3  
  • Derive  your  Backlog  from  the  Vision   For  whom?   Completes   Why?   and  refines   What?   the  vision   Product  Vision   Product  Backlog   Makes   Shared   the  vision   hypothesis   implementable  ©  2011  Pichler  ConsulDng  Limited   4  
  • Ensure  your  Backlog  is  Very  DEEP   Detailed   Visible   appropriately   PrioriDsed   Emergent   Product  Backlog   EsDmated  ©  2011  Pichler  ConsulDng  Limited   5  
  • Keep  your  Backlog  Concise   •  Think  big  but  start  small   –  Restrict  your  iniDal  product  backlog  to  about  40-­‐50  items   –  Keep  the  majority  of  the  items  coarse-­‐grained   •  Use  the  vision  to  decide  if  an  item  should  be  added   or  removed   –  Only  add  items  that  help  you  turn  the  vision  into  a   successful  product  –  assuming  your  vision  is  valid  ©  2011  Pichler  ConsulDng  Limited   6  
  • Let  your  Backlog  Emerge   Product   Backlog   Working   Change   Soware   Feedback   Learning   Customers  and  users  ©  2011  Pichler  ConsulDng  Limited   7  
  • Groom  your  Backlog  Regularly   •  Discover  and  describe  new  items,  adjust  or   remove  exisDng  ones   •  PrioriDze  the  product  backlog  items   •  EsDmate  the  items   •  Prepare  the  high-­‐priority  items  and  get  them   ready  ©  2011  Pichler  ConsulDng  Limited   8  
  • Groom  CollaboraDvely   Customer   Marketer   Product  Owner   Development  Team   Salesman   User   Service  Rep  ©  2011  Pichler  ConsulDng  Limited   9  
  • Use  Stories  Wisely   •  Start  with  big,  coarse  grained  user  stories  (epics)   •  Add  detail  based  on  customer  and  user  feedback   –  Decompose  the  stories  progressively  driven  by  their   priority   •  Apply  the  3C  criteria  to  your  stories   –  Card   –  ConversaDon   –  ConfirmaDon  ©  2011  Pichler  ConsulDng  Limited   10  
  • Get  the  Backlog  Ready   Ready   Working Software Ready = Clear + feasible + testable©  2011  Pichler  ConsulDng  Limited   11  
  • Don’t  forget  the  “iliDes”   OperaDonal  qualiDes   Product  and  user   Such  as  performance,   interface  design   robustness,  compliance,   Employ  sketches  and   interoperability,  and   screen  shots   security     Global Performance Constraint The system must answer any request in less than a second.©  2011  Pichler  ConsulDng  Limited   12  
  • Try  my  Product  Backlog  Board   Story  Area   Constraint  Area   OperaDonal   Product  and   1.  Story   2.  Story   3.  Story   4.  Story   Ready     QualiDes   UI  Design   Items   5.  Story   6.  Story   7.  Story   8.  Story   Performance   Constraint   Epic   Epic   Theme  A     Epic   Epic   Epic   Robustness   Constraint   Epic   Epic   Theme  B     Epic   Epic   Interop.   Constraint   Theme  C     Epic   Epic   Epic  ©  2011  Pichler  ConsulDng  Limited   13  
  • The  Reward  is  Sweet  
  • CONSULTINGAND TRAININGIN AGILEPRODUCTMANAGEMENTAND SCRUM Contact details: +44 (0) 7974 203772 roman.pichler@romanpichler.com @romanpichler www.romanpichler.com www.allthingsproductowner.com