Join Doug Rose for an in-depth discussion in this video Refining the backlog, part of Agile at Work: Reporting with Agile Charts and Boards.
- The product backlog is always changing.…The product owner should work on the list several…hours a week.…They'll be clarifying the stories, and adding new ones…as they find more work.…In scrum's early years, this was called backlog grooming.…The scrum community later changed this term,…they settled on the term backlog refinement.…Whatever you call it, the activity is pretty much the same.…In your backlog you typically have a list of user stories.…This is often called your product backlog items,…or PBIs.…
You refine the backlog by adding, removing,…or updating these backlog items.…Refinement is probably not the best place to start.…In the beginning, you'll mostly be adding stories.…It doesn't seem like refinement, if your backlog…continues to grow.…Later, the product owner prunes down these items…to get a clear list.…It's better to think of this early activity…as backlog preparation.…The product owner should spend four to eight hours…a week working with the team to refine the product backlog.…
Anything longer, and the team will start to lose focus.…
Bonus: Watch the bonus chapter at the end of this course where Doug answers common questions about the agile mindset, including what types of projects would be the best fit.
Lynda.com is a PMI Registered Education Provider. This course qualifies for professional development units (PDUs). To view the activity and PDU details for this course, click here.
The PMI Registered Education Provider logo is a registered mark of the Project Management Institute, Inc.
- Communicating progress
- Prioritizing the backlog
- Showing daily progress with a taskboard
- Sizing taskboards
- Creating a burndown chart