This document provides an overview of techniques and templates used in advanced product owner workshops, including lean canvas, user personas, user story templates, prioritization methods like MoSCoW and Kano model, acceptance criteria templates, techniques for splitting stories, progress tracking methods like burn-down charts and impact mapping, and exercises for estimating project costs based on representative story points and development times. Key terms and practices in agile product management and development are also defined.

1. ADVANCED
PRODUCT
OWNER
WORKSHOP
PARTICIPANT HANDBOOK
Page of1 10 PO Workshop Handouts

2. Lean Canvas
User Personas
Page of2 10 PO Workshop Handouts

3. User Stories Recommended Templates
Option I: As a <WHO> I want to <WHAT> so that <WHY>
Option II: In order to <WHY> As <WHO> I want to <WHAT>
Prioritizing User Stories
MoSCoW
Simple Risk Analysis
Page of3 10 PO Workshop Handouts

4. Prioritising using Kano model
Negative Question
Question I like
it
It Must
be
I’m
neutral
It’s
OK
I
dislike
it
Positive
Question
I like it Q E E E L
It must be R I I I M
I’m neutral R I I I M
It’s OK R I I I M
I dislike it R R R R Q
Legend
M Mandatory
L Linear
E Exciter
I Indifferent
R Reverse (can be
either way)
Q Questionable
Requirement M L E I R Q Result
Page of4 10 PO Workshop Handouts

5. Braking/Splitting Stories Strategies
Acceptance Criteria Recommended Template
GIVEN a pre-condition
WHEN an action happens
THEN an expected result occurs
Page of5 10 PO Workshop Handouts
Vague terms
Identify vague terms in your story and
refine them as different user stories
As a manager I want a report so I can
make better decisions
Conjunctions
Split around AND, OR, WHEN, IF
As an operator I want to a report on
screen, PDF and mobile, so I can…
Acceptance Criteria
Each criteria can go to its own story
Successful login
2-ID login
Wrong password…
Workflow Steps
Each step in the flow can be its own
story
Log-in, Add service, Publish service, Set
price, Get quote, Get payment, Send
invoice, … Close transaction
Operations (e.g. CRUD)
As a user, I can manage my account.
...I can sign up for an account.
...I can edit my account settings.
...I can cancel my account.
Business Rule Variations
As a user, I can search for flights with
flexible dates.
...as “n days between x and y.”
...as “a weekend in December.”
...as “± n days of x and y
Major Effort
As a user, I can pay for my flight with
VISA, MasterCard, Diners Club, or
American Express.
...I can pay with one credit card type
(of VISA, MC, DC, AMEX).
...I can pay with all four credit card types
(VISA, MC, DC, AMEX).
Data Entry Methods
As a user, I can search for flights
between two destinations.
...using simple date input.
...with a fancy calendar UI.
… …

6. Progress Tracking
Page of6 10 PO Workshop Handouts

7. Impact Mapping
http://impactmapping.org/drawing.php
Estimating Projects Exercise
You need to estimate the cost of the following project:
The overall project size is estimated at 500 points (relative size)
The project team chose 3 representing stories, and estimated their
development effort:
You need to estimate cost for the entire 500 points.
Story Relative size Estimated man days Days per point
A 8 points 20
B 13 points 40
C 5 points 10
Page of7 10 PO Workshop Handouts

8. Page of8 10 PO Workshop Handouts

9. Page of9 10 PO Workshop Handouts

10. Across
3. A practice to articulate the vision of the product
6. A practice to characterise the typical users of a service or a product
11. The acronym that defines the characteristics of great agile
specifications (or tests)
14. A semi-formal method to use an algorithm to estimate the cost of a
software project
15. The accumulated undone work that slows a development team down
17. A Japanese expert who devised an award-winning practice for
prioritising requests
18. The activity to clarify, split and estimate requests
20. A practice that uses the timeline of using a service or product to
generate prioritised requirements
Down
1. A common practice to articulate agile requirements
2. The set of terms between the Product Owner and team that reflects
the current standards of a development team
4. A chart that reflects the evolving amount of remaining work to be done
5. An experiment to validate business assumptions
7. Based on experience, rather than on pure logic
8. A common term for agile relative estimation units
9. The acronym that defines the characteristics of great agile
requirements
10. a mind-map to visualise requirements by answering why a product
or service is needed, who can help making it, what can they do, and
how can we get them to do it
12. The camel annotation of the practice to prioritise according to must-
haves, should-haves, could-haves and won’t-haves
13. A traditional way to define the milestones for a product or a major
release
16. Card, Conversation, Confirmation
19. A syntax for writing specifications (or tests)
Page of10 10 PO Workshop Handouts