Understand how the Agile Manifesto impacts the Scrum framework, and get an introduction to the roles and cycles used in Scrum.
As product owner, you need to know to develop a charter for your product that inspires team commitment and results in a clear goal. You’ll also receive valuable templates to help communicate your product vision so that it is compelling and actionable.
The product backlog is the central nervous system of any Scrum project. As product owner, you need to know how to prioritize, refine and maintain it so that the team is always working on priority items without facing unnecessary delays.
You’ll also discover how to use iterations to turn epics and themes into useful user stories that are clear and ready for the team to develop.
Learn how the three Scrum roles of product owner, Scrum Master and team work together using Scrum. As product owner, you’ll also understand what is expected from you in terms of availability, decision-making and your relationship with stakeholders.
Learn more than how a sprint plan works. Find yourself equipped with skills to manage the complexities that can disrupt progress. What should you do if a team falls behind? When should work be added or dropped from a sprint? And when should you abnormally terminate a sprint?
Creating accurate estimates of when something will ship and what it will do provides confidence for stakeholders and encourages commitment from technical team members. In this course, you’ll learn about story points, the top misunderstanding that prevents teams from using them successfully, and use Planning Poker to estimate them as a group. As a product owner, this lets you make long-terms plans more easily and prioritize stories for the team.
Master a step-by-step, methodical system for prioritizing. You’ll discover how to identify which features are mandatory, linear or exciters, and then find out how to aggregate and weigh results based on importance. The result is a prioritized product backlog that is easy to follow and deliver.
Using velocity ranges, you’ll develop a system for making accurate estimations for fixed-date and fixed-scope projects. You’ll also understand how technical debt may affect your progress and how burndown charts can quickly show the team’s progress.