Difference between revisions of "Certified Scrum Product Owner Course"
(21 intermediate revisions by the same user not shown) | |||
Line 23: | Line 23: | ||
− | == Prerequisites == | + | == Prerequisites: Pre-readings == |
− | + | Participants must read (available online), before the course: | |
− | * | + | * [https://www.scrum.org/Scrum-Guide The Scrum Guide] |
− | + | * [http://scrumprimer.org/ Scrum Primer] | |
− | + | * [http://www.craiglarman.com/wiki/downloads/scaling_lean/larman-vodde-feature-teams.pdf Feature Teams] pp 150-156 only, or the equivalent section in ''Feature Teams'' in [[Book_-_Scaling_Lean_and_Agile_-_Thinking_and_Organizational_Tools | Scaling Lean & Agile Development]] | |
− | + | * [http://www.scrumalliance.org/resources/1122 Kicking ScrumBut] | |
− | |||
+ | Unless otherwise arranged, every participant is also required to have read the following chapters from [[Book_-_Practices_for_Scaling_Lean_and_Agile | Practices for Scaling Lean & Agile Development: Large, Multisite, & Offshore Product Development with Large-Scale Scrum]] (Larman & Vodde), before the course: | ||
+ | * Chapter 3: Product Management | ||
+ | * Chapter 8: Requirements & PBIs | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
+ | ...And the following chapters from [[Book_-_Scaling_Lean_and_Agile_-_Thinking_and_Organizational_Tools | Scaling Lean & Agile Development: Thinking and Organizational Tools for Scrum]] (Larman & Vodde), before the course: | ||
+ | * Chapter 2: Systems Thinking | ||
− | |||
− | |||
− | |||
− | |||
− | |||
+ | NOTE! Your company may have an online [http://my.safaribooksonline.com/ Safari] account that you can use to read the book chapters online free. Please ask your colleagues if you have a Safari account. | ||
+ | <br> | ||
+ | <br> | ||
== Outline == | == Outline == | ||
− | * Why is the Product | + | * Why is the Product Owner role so central to Scrum and what will you do that’s new? |
− | * | + | * Agile Values |
− | * | + | * Scrum Background |
− | * | + | * Lean Thinking |
− | * | + | * Outcomes versus Outputs |
− | * | + | * Outcome-driven Scrum |
− | * | + | * Impact Mapping for Outcomes |
− | * | + | * Measurement Points in Impact Mapping |
− | * Ideation for Innovation | + | * Reducing Waste in Product Management |
− | * | + | * Iterative and Evolutionary Development |
− | * | + | * Definition of Done |
− | * | + | * Release Sprint |
− | * | + | * Adaptive Planning |
− | * | + | * Initial Product Backlog Creation |
− | * | + | * Sprint Review |
− | * | + | * Ideation for Innovation |
+ | * Innovation Games and Game Storming | ||
+ | * Story Mapping | ||
+ | * Product Backlog Prioritization with Relative Points | ||
+ | * Product Backlog Prioritization with Attribute Classes | ||
+ | * Estimation, Release Planning and Scheduling | ||
+ | * Estimating with Monte Carlo Simulation | ||
+ | * Stories and the 3Cs | ||
+ | * Specification by Example | ||
+ | * Business Benefits | ||
+ | * Changes for the Product Owner | ||
+ | * Kano Model | ||
* Fixed-Price, Fixed Time, Fixed Scope: Can You Have Your Cake and Eat it Too? | * Fixed-Price, Fixed Time, Fixed Scope: Can You Have Your Cake and Eat it Too? | ||
− | |||
− | |||
− | |||
* Product Backlog grooming or refinement | * Product Backlog grooming or refinement | ||
− | |||
* Tracking Progress in Scrum | * Tracking Progress in Scrum | ||
− | |||
* Further education resources for Product Managers | * Further education resources for Product Managers | ||
− | |||
− | |||
== Maximum Participants == | == Maximum Participants == | ||
− | + | 30 | |
== Environment - Room, Tools, Texts == | == Environment - Room, Tools, Texts == | ||
Read this: [[Course Environment - Workshop Style1]] | Read this: [[Course Environment - Workshop Style1]] | ||
− | |||
− | |||
− | |||
− | |||
− |
Latest revision as of 13:30, 3 October 2015
Contents
Overview
2 days
There’s a revolution sweeping the product development world: agile methods. Some Product Managers (sometimes called the Business Owner of the system, for internal systems) and development teams have been applying these practices for years, and they are now spreading worldwide, from London to Los Angeles.
In Scrum, the most popular agile method, a key role is Product Owner. This is a product management role with specific responsibilities in Scrum: responsible for the ROI, release date, release content, and choice of goals each Sprint. In this practical, information-and-tips-packed seminar you will learn the key ideas and practices of agile development, aimed at Product Managers and the Scrum Product Owner.
Methods of Education
Discussion, presentation, Q&A, workshop exercises
Audience
Those involved in product management
Level
Introductory-Intermediate
Prerequisites: Pre-readings
Participants must read (available online), before the course:
- The Scrum Guide
- Scrum Primer
- Feature Teams pp 150-156 only, or the equivalent section in Feature Teams in Scaling Lean & Agile Development
- Kicking ScrumBut
Unless otherwise arranged, every participant is also required to have read the following chapters from Practices for Scaling Lean & Agile Development: Large, Multisite, & Offshore Product Development with Large-Scale Scrum (Larman & Vodde), before the course:
- Chapter 3: Product Management
- Chapter 8: Requirements & PBIs
...And the following chapters from Scaling Lean & Agile Development: Thinking and Organizational Tools for Scrum (Larman & Vodde), before the course:
- Chapter 2: Systems Thinking
NOTE! Your company may have an online Safari account that you can use to read the book chapters online free. Please ask your colleagues if you have a Safari account.
Outline
- Why is the Product Owner role so central to Scrum and what will you do that’s new?
- Agile Values
- Scrum Background
- Lean Thinking
- Outcomes versus Outputs
- Outcome-driven Scrum
- Impact Mapping for Outcomes
- Measurement Points in Impact Mapping
- Reducing Waste in Product Management
- Iterative and Evolutionary Development
- Definition of Done
- Release Sprint
- Adaptive Planning
- Initial Product Backlog Creation
- Sprint Review
- Ideation for Innovation
- Innovation Games and Game Storming
- Story Mapping
- Product Backlog Prioritization with Relative Points
- Product Backlog Prioritization with Attribute Classes
- Estimation, Release Planning and Scheduling
- Estimating with Monte Carlo Simulation
- Stories and the 3Cs
- Specification by Example
- Business Benefits
- Changes for the Product Owner
- Kano Model
- Fixed-Price, Fixed Time, Fixed Scope: Can You Have Your Cake and Eat it Too?
- Product Backlog grooming or refinement
- Tracking Progress in Scrum
- Further education resources for Product Managers
Maximum Participants
30
Environment - Room, Tools, Texts
Read this: Course Environment - Workshop Style1