Join Doug Rose for an in-depth discussion in this video Creating the product backlog, part of Agile at Work: Reporting with Agile Charts and Boards.
- In traditional project management…the team relies on completed requirements…before the work begins.…In Agile, the backlog replaces these requirements.…The product backlog is a ranked list of user stories.…These stories drive the project.…In Agile, the backlog doesn't try to capture all the work.…Instead, it's an ever changing document.…The product owner has the sole authority…to add or change the work to the backlog.…Then the list gets reprioritized based on the changes.…
The highest value stories are reordered…and pushed to the top.…If you're the product owner,…then the best way to start the backlog…is by creating a few high-level user stories.…These stories might start out vague.…Chances are they'll be Epics…and you'll have to break them down into clear stories.…Your backlog might just start out as a clumsy wish list.…Then you'll refine the backlog over time.…You'll make it clear.…Each update will get better and better.…A good way to think of your backlog…is to think of it as your project's Pez dispenser.…
A Pez dispenser is a little candy case…
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.
- Explain the purpose of a taskboard and how it can help keep a project on track.
- List the correct order of the swim lanes on a taskboard.
- Name the two types of burndown charts.
- Recognize the problems that occur when a team does not break down epics into stories.
- Identify the three roles in the triangle of responsibility.