Class
CSPO Certified Scrum Product Owner
Taught by James O. Coplien
March 18-19, 2013 in Tampere, Finland
The Product Owner is the strong — or weak — link in successful Scrum products. Do you know how to write an enabling specification? Do you know how to drive your team to success? Come and direct this course where you need it to go — because you’re the boss!
Registration for this class has closed.
Venue
Edutech, Hermiankatu 1, 4th Floor, Hermia, Tampere, Finland FI-33101
Questions?
Description
This unique Product Owner certification course teaches you the basics of running a project using Scrum. You’ll learn that You’re the Boss, and that you’re in command — yet your team is in control. You’ll learn the balance of power and governance between the Product Owner, the Team, and the ScrumMaster that make Scrum an effective framework for achieving business goals.
Because You’re the Boss, you build this course yourself from a product backlog that’s already been estimated by the team (the course instructor). You’ll learn right away the importance of choosing must-haves for the market, of honoring dependencies between Product Backlog Items (PBIs), and of getting the most value for your time — all in the first half hour! How it proceeds from there is your choice. Choose from topics in areas such as:
- Intro to Scrum
- The product backlog
- Product Owner Team
- The Process
- Business Concepts
- The Product Owner in the Organization
- … or create your own!
See the Agenda below for more information.
We’ll also go in-depth to cover User Stories, traditional requirements, features, Use Cases, and issues, and their strengths and weaknesses as PBIs. We’ll take a broad, all-encompassing look at ROI, and look at Agile Contracts: change for free and money for nothing!
Agenda
The agenda will be chosen by the class from the following items (* = required for certification):
- Vendor management
- Scrum basics *
- Your product backlog
- The Product backlog *
- Requirements as product backlog items (depends on #4)
- Poker Planning * (is done as part if #10)
- Enabling Specifications *
- The Product Owner team
- Customer Engagement *
- Team Engagement *
- Process Improvement
- Sprint Planning *
- Release Planning * (depends on 12)
- Sprint Backlog & task board
- The Daily Scrum
- Burn-Down Charts (depends on 14)
- “Done” and technical debt
- Emergency procedure * (depends on #8, #10, #12, #14)
- Sprint Review *
- ROI and Risk Management
- Supplier Management (depends on #4)
- Agile Contracts (depends on #4)
- The MetaScrum (depends on #8, #10, #11, #13 and #26)
- Separation of Command and Control (depends on #17)
- Scaling Scrum
- Value Calculation (depends on #37)
- Boss /Worker game
- Spec /Developer game (depends on #4)
- ROI exercise (depends on #20)
- Overview of Product Backlog items (depends on #4)
- Examples of Product Backlog Items (alternative to #4)
- Feature-based Product Backlog Items (depends on #4)
- User Stories as Product Backlog Items (depends on #4)
- Use Cases as Product Backlog Items (urgently recommended; depends on #4)
