top of page

Product Ownership Workshop

Who Should Attend?

  1. Business Analysts who want to become Product Owners or move into Consulting

  2. Business Consultants who want to sharpen their Product Ownership toolkit

  3. Product Owners who want to manage a project in delivery better

  4. General Interest in the role before applying to Product Owner opportunities

Course Outline

Course Outline:

The Technology Product Ownership workshop is a scenario project-based experience. The workshop is designed from the employer’s perspective. As such, it is meant to enable participants to immediately apply the tips, tricks and techniques in their immediate practice.

This two-day workshop emphasizes Strategic Analysis in evolving ideas to deliver a concrete product vision, an executable roadmap, and an understanding “good” story founded on concrete acceptance criteria. At the core of this workshop is the Product Owner’s ability to showcase their thought leadership and understand their roles and responsibilities to enable the entire project team to achieve product outcomes.

Duration: 15 Hours (2 full-days or Consecutive 4 half days)

When: Every Saturday and Sunday or private booking during the week (please send email to register)

Where: Virtual (Sessions are not recorded)

Module Breakdown:

Day 1:

Module 1: Not all Ideas are “good”

1.1 PO accountabilities start with you

1.2 Alignment to Corporate Direction (Capability Model / Framework)

1.3 Why “now” – Idea in an investment with return (review the project delivery framework – agile, waterfall)

1.4 No Product without a Problem or Opportunity (Techniques)

1.5 Workshop Case Study – Let’s Go

1.6 Solidifying the “Idea” Opportunity Assessment

Module 2: Cost to Product Ownership Rationale for Minimum, not Maximum Viable Product

2.1 What’s the cost to operationalize and maintain? (flow out the model, assign people, tech cost)

2.2 Prioritizing Opportunities to Create a Roadmap – (ensure alignment and funding, people readiness, where on the roadmap)

2.3 Define MVP - not maximum but minimum (HLR back to Capability Model)

2.4 Identify business solution options - bare bones - think differently (use click to chat as a sample – review the case study to show think differently)

2.5 Prioritizing Stories Understanding Complexities

Day 2:

Module 3: Recognizing Good Stories and Acceptance Criteria

3.1 Unravelling User Story Complexities

3.2 Delivery Strategy – Working authorities, managing expectations

3.3 Stop Meeting for the sake of meetings

3.4 User Functional Interaction

3.5 The story doesn’t work without NFRs

Module 4: Product Quality Outcomes

4.1 Measurable Investment Outcomes

4.2 Backlog Grooming and Product Roadmap

4.3 Enabling User Adoption

4.4 Product Ownership Summary

bottom of page