Lean lessons learned - lean startup methodology and lessons learned from Blossom
Lessons Learned in Product Ownership
-
Upload
kent-mcdonald -
Category
Software
-
view
177 -
download
3
Transcript of Lessons Learned in Product Ownership
KnowledgePartnersbridge
Kent J. McDonald @beyondreqs
Lessons Learned in Product Ownership
What is Product Ownership, really?
Outcome over
Output
Make sure decisions are
made
User Experience
Product Management
Business Analysis
We want to
be here.
Models
Tactics PO’s Use
Decision
Filters
Collaborative Modeling
ABC Priority
Story Splitting
Examples
Acceptance
Criteria
Stock the backlog
Refine the backlog
Describe backlog items
3 Most Common Product Owner/BA models
Biz Leader
PO Delivery Team
Biz Leader
PO Delivery Team
Biz Leader BA Delivery
Team
Business IT or Product Development
Customer
Note: Biz Leader is a Product Manager in Product Development context
Source: Todd Little Vice President IHS
The Submission System
Change in the Review Process
Review Process Agile2013
Process Tweak Agile2014
Thou (review committee) shalt… Reviewth each session once within one week Revieweth each session thrice within two weeks
The Result
Process Tweak
Agile2015
From Quantity to Quality
Des
cribing the ch
ange
We started with this
Save a Dra<
What do you want to do now? Click one of the buEons below:
Get Some Help
SUBMIT FOR EVALUATION
Why should I “Save a Dra>”? You can save a dra< as many Jmes as you need. Once saved, your submission will be available for your friends and colleagues to give feedback on via public comments. The Program Teams WILL NOT see your submission for evaluaJon.
Why should I “Get Some Help”? If you are struggling with your submission, you can request feedback from Agile Alliance shepherds who can help you prepare your submission to be as good as possible for evaluaJon for inclusion.
Why should I “SUBMIT FOR EVALUATION”? Once you are very sure you’re submission is ready to be considered, submit it. It will only be evaluated once you have pressed this buKon.
THE REST OF THE SUBMISSION FORM IS ABOVE
And got som
e feedback…
“No process survives first contact with the program
team” -‐ Helmuth Von Moltke, (sort of…)
Actual Quote: “No operation extends with any certainty beyond the first encounter with the main body of the enemy.”
Lessons Learned
Sometimes you
need to
change the
goal
Find the simplest thing that will work then enhance with feedback UX Matters
If you don’t tell people
new process, they’ll make
one up
Validate
assumptions
early and
often
SME’s are not the only source of useful
feedback
Talk amongst yourselves
I’ll give you a topic. 1) What would you have done in my situation? 2) How might you apply these ideas in your setting? Discuss.
Movie Phone Estimating
Why don’t you just tell me your budget?
ABC Prioritization
1. Group into A, B, C 2. Ask for budget
constraint 3. Can we get A done
within budget constraint?
Will have (A)
Might have (B)
Won’t have (C)
Estimates at high end
Estimates at low end
Lessons Learned
Budgeting
instead of only
estimating
changes the
conversation
Items in A should only take up about 50% of capacity
If estimating
in ranges, total
max value of
all A items
If total of A items exceeds budget, decide ask for more, or change A
Find a way to
track progress
along the way,
to know if any
B will get in
Wide ranges ok, indicate
greater uncertainty.
Talk amongst yourselves
I’ll give you a topic. 1) What would you have done in my situation? 2) How might you apply these ideas in your setting? Discuss.
Unintended Consequences
Email Gherkin
Given Jon is a
reviewer on UX
track
When Adrian
submits session
Then he receives
thanks msg
When Jon provides feedback Then Adrian receives
notification When Adrian
responds to Jon’s
feedback
Then Jon receive
s
notification When Jon responds to his own feedback Then No notification is sent
When Adrian replies to Jon’s response Then Jon receives notification
When Jon responds to his feedback in reply to Adrian Then no notification is sent
The Rules (as built)
1. Submitters receive notification when someone has left them feedback
2. The person who left the feedback receives notification when someone responds to that feedback.
3. The person who responds to feedback receives a notification when someone replies to their response.
4. A person who replies to herself will not receive a notification.
Lessons Learned
UX matters
Process changes often drive
unintended consequences
Some problems
hide until the
conditions are
right to spot
them
Some problems are not worth solving right
now.
“It’s broken”
may mean “It
doesn’t work
like I’d expect”
Examples are very powerful when trying to figure out the root cause
Talk amongst yourselves
I’ll give you a topic. 1) What would you have done in my situation? 2) How might you apply these ideas in your setting? Discuss.
What did you find useful?
@beyondreqs, when I go to work on monday, I’m going to try… #baot
Questions?
Stay in Touch
Kent McDonald
@beyondreqs
www.beyondrequirements.com
Slides available from: http://www.slideshare.net/kentjmcdonald