In this video Angela explains what a product backlog is, why it exists, and the agile product owners’ role with the backlog. She will also cover what a good backlog looks like and how an initial backlog may get created. This tutorial also covers the levels of detail in a backlog and how the team can use the different levels of detail to keep the backlog well organized and managed.
- So, you're assigned a new project…or perhaps you've inherited one…and you're the product owner.…Whatever the case, the team needs a backlog to get started.…A backlog is a prioritized list of…what the team will deliver.…It represents a view of all the items…that are in queue for the team to work on.…Backlog ideas usually come from you as the product owner…from your work decomposing the product roadmap.…It's also common that others have submitted ideas…that you need to analyze and use…when creating a backlog.…
You may be thinking if you're handed a list,…why create a backlog, isn't it already done?…Prioritizing and analyzing the backlog…for gaps and the correct levels of detail…is no easy task.…Many refer to this activity as refining the backlog…and it's an ongoing and major responsibility…of the product owner.…So, what does a good backlog look like?…Well, many teams and descriptions…have us picturing a stacked lists of…requests, requirements, enhancements and stories.…
I like to think of a backlog as a funnel…of multiple levels.…
- Identify the goals of a product owner on an agile team.
- Explore the essentials of an agile roadmap.
- Examine the elements of an agile planning overview.
- Identify key agile product owner competencies.
- Recognize the fundamentals of the experimenting and prototyping phase of agile planning.
- Discover common myths of agile product ownership.