Agile and Lean Product Owner Workshop

Are you working as a Product Owner? Are you unsure how your responsibilities differ from the Scrum Master, project manager or program manager? Are you working to be agile, but not sure you can be? Do the developer teams pressure you for “technical” stories instead of end-to-end features? Maybe you need this workshop.

Workshop Objective: The Agile Product Owner represents the business objectives to the team. The product owner determines the value of the features, decides on the minimum viable product, and rank-orders the features in the backlog. Some people claim it’s an impossible job. It’s not. It is, however, a critical role for the team.

In this workshop, you’ll experience how to be an effective product owner, from managing the agile roadmap to managing the backlog for an iteration. We will also practice release planning, with and without estimation.

Workshop Overview: In this workshop, we’ll practice agile roadmapping with your features and products. You will learn how to evaluate features, epics, and themes, not based on estimates, but based on business value, which includes cost of delay and possibly a gross estimate. After learning to create a roadmap, we will practice creating story decomposition for value. We will practice defining a minimum viable product, and what to do when you realize your minimum viable product is not minimum or viable.

Target Audience: Product owners and their teams, program managers and their program product owners, others interested in the product owner function.

Prerequisites: Experience on an agile project or an agile program, preferably for at least one year.

Workshop Duration: 2 to 3 days, depending on the practice for your products we build in.

Workshop Outline

  1. Introduction
    • Workshop purpose and expectations
    • What is Product Ownership
    • How agile and lean help
  2. Organize the product
    • The agile roadmap
    • Features (stories), epics, themes
    • Activity and debrief
  3. All about stories
    • Who the story is for
    • What is the value
    • Activity and debrief
  4. Define minimum viable product
    • How minimum is minimum
    • How often can your team release?
    • Activity and debrief
  5. Principles that you want to consider
    • Small and continuous
    • Simulation and debrief/Practice with your features
  6. Release planning
    • Options for release planning
  7. Separate the problem from the design
    • What the team does and what you do
    • Value and estimates
    • Story decomposition for value
    • Activity and debrief
  8. When you see the demos
    • Don’t wait for the end of the iteration
    • How to balance your work
    • Replanning based on what you see
    • Exposing interdependencies
    • Moving to continuous integration
    • Measurements
  9. Summary and wrapup

Leave a Comment

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: