The Product Owner role is arguably the most important role in Scrum — and the most challenging. The Product Owner is part project manager, part product manager, and part customer advocate. This person must ensure the customer’s wants and needs are understood while ensuring that the team delivers the greatest-value features as quickly as possible — all while responding to ever-changing requirements. Ultimately, the Product Owner owns a Scrum project’s success or failure.
PMI PDU Reporting Instructions
This Scrum Product Owner eLearning course drills down into the detailed information needed to successfully plan releases, reflect stakeholder priorities, ensure the team builds the right product, and communicate with marketing, sales, executives, and other project stakeholders.
Who Should Attend?
This online seminar is for technical project managers, program managers, and product managers who are transitioning to the Scrum Product Owner role.
It All Starts With a Vision
The Product Owner’s View of Scrum
- What is Scrum?
- How it works
- Scrum Roles, Processes and Artifacts
The Successful Product Owner
- Technical… enough
- Product Owner, Project Manager, or Product Manager?
- Attributes of successful Product Owners
What Are We Trying to Build?
- What is a requirement?
- The Product Vision as the top-level requirement
- Three purposes of requirements
- Using requirements to manage risk
- Product versus project requirements
- User stories and acceptance criteria
- The Definition of Done and why it matters
How Will We Build It?
- Successful Scrum projects require planning
- The Product Backlog
- Creating a product roadmap
- Release planning
- User Story Mapping
- Incremental Delivery via sashimi Implementation
During the Game
- Product backlog grooming
- Sprint planning
- Sprint reviews and retrospectives
- Dealing with change
- Scrum project tracking
Construx Senior Fellow
Earl Beede, CSDP is a Senior Fellow at Construx Software, where he designs and leads seminars and provides consulting services on early project-lifecycle practices, estimation, requirements, quality assurance, contract management, and software methodologies.
With more than 20 years experience as a quality assurance representative, systems analyst, process architect, and manager, Earl has designed and written software development processes for companies across a wide variety of industries. Prior to joining Construx, he held quality assurance and systems analyst positions at organizations that include the Department of Defense, Boeing Computer Services and Verizon Wireless.
Earl has a Bachelor’s degree from the University of Washington. He is a member of the IEEE Computer Society and a past coordinator of the Seattle Area SPIN (Software Process Improvement Network).