Learn how to create and refine a product backlog as well as how to identify when the product owner is in jeopardy of losing important authority.
- 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 wishlist. … Then you'll refine the backlog over time. … You'll make it clear, … each update will get better and better. … Not every organization will respect …
- 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.