Whatever framework a team uses, someone has to decide what is worth building and in what order. This module looks at product ownership: the accountability for maximizing the value of the product, and the backlog that makes those decisions visible to everyone.
You'll start with the Product Owner role, including what it owns and where it often goes wrong. Next you'll look at how a Product Backlog is built and refined, from epics and user stories to items small and clear enough to be worked on. The module closes with prioritization techniques such as MoSCoW, RICE, and value versus effort, and when each one helps or misleads.
With a healthy backlog in place, you'll be ready for the next module, Estimation, Planning & Forecasting, where you look at how teams size work and predict when it will be done.
What the Product Owner is accountable for, how the role connects the team, stakeholders, and customers, and the common ways it is weakened, such as proxy POs and absent decision-makers.
How a Product Backlog is shaped and kept healthy through continuous refinement, including writing user stories, splitting epics, and getting items ready for the team.
A comparison of common ordering approaches, including MoSCoW, RICE, and value versus effort, and guidance on choosing the right one for the decision at hand.