Upload
xebia-it-architects
View
515
Download
0
Tags:
Embed Size (px)
DESCRIPTION
AgileNCR 2010 conference was held in Gurgaon on 17th & 18th July 2010. This largest community driven conference was the Fourth edition of Agile NCR and was organized in collaboration with ASCI. This time the event was based on four major themes : 'Agile for newbies', ' Agile Adoption Challenges', 'Workshops and Software Craftsmanship', and ' Post Agile'.
Citation preview
A Presentation on Product Owner personas
7/18/2010 2
Chris does not control his backlog.
Multiple customers input needed for backlog
7/18/2010 4
0 Great at Herding Customers
7/18/2010 5
He knew the business well
When in Ask
7/18/2010All rights reserved Vibhu Srinivasan
6
How much time did he spend with the team
40 % 7/18/2010
All rights reserved Vibhu Srinivasan7
Wait aren’t Product owners needed to spend all their time
with their teams
Says- FOCUS ON YOUR CUSTOMER NOT THE TEAMS
7/18/2010 8
POT ? Meets twice a week
Product owner Team Meeting
Customer Ideas
Roadmap
Release Plan
Product
Product Backlog
Vision
Velocity
Inputs:
Participants:
User Story Workshops, Cust Interviews
One Backlog
Outputs:
Product Backlog
Copyright © 2007 – 2010
SolutionsIQ. All Rights Reserved.
Says
7/18/2010 10
“My top most priority is the
backlog readiness”
He is quick to decide once data is available. Takes Calculated
Risks
7/18/2010 11
Team first, Customer First Attitude
7/18/2010 12
But the most important trait of all…..
7/18/2010All rights reserved Vibhu Srinivasan
13
For him..
0Scrum was just a tool So he wouldn't lose sleep for a deviation he took
7/18/2010 14
No Lost in Translation
Encouraged Team To Sign Up For Really Complex Stories
0 Teams were allowed to talk to any customer Directly within a sprint
7/18/2010 15
Its not done until everything is done
ESP. TESTABLE CODE
7/18/2010 16
Says
Final Thoughts
0 Chris’s teams produce complex software, ship it and deploy it to multiple deployment centers across the world pretty touch free and with Zero Major Defects – EVERY TWO MONTHS
0 Customers in this case are extremely satisfied with Chris and his products.
7/18/2010All rights reserved Vibhu Srinivasan
17
A bit about Happy Jen
0 Very approachable product manager
0 The company grew too quickly so Jen went from one product one team to many products many many teams quickly.
0 No knowledge of Scrum, but dealt with teams that were highly scrum aware.
7/18/2010All rights reserved Vibhu Srinivasan
19
Once upon a time …
7/18/2010All rights reserved Vibhu Srinivasan
20
0 One Visionary , Big B, Many followers
0 Developers developed whatever Big B wanted
0 They shipped whenever
Then came Jen
7/18/2010 21
0 Took over the product from the visionary.
0 Built some basic process like initial documentation of requirements
But
The teams continued to see Jen as a proxy product owner as
Big B The visionary continued to directly interact with
teams
7/18/2010 22
Soon productgrew
7/18/2010 23
1
1
BACKLOG
BIG BACKLOG
Product became a portfolio
7/18/2010 24
0 1 3 42
Jen Pondered !!One or Many Backlogs?
7/18/2010 25
ONE BIG
BACKLOG
BACKLOG 1
BACKLOG 2
BACKLOG 3
BACKLOG 4
OR
They Chose
0Many Backlogs
7/18/2010All rights reserved Vibhu Srinivasan
26
Which then led to the question ??
0 ONE TEAM PER BACKLOG OR MANY TEAMS PER BACKLOG
0 AND ONE PRODUCT OWNER PER BACKLOG OR JUST JEN
7/18/2010 27
One Product owner –Many teams
7/18/2010
All rights reserved Vibhu Srinivasan28
BACKLOG 1
BACKLOG 2
BACKLOG 3
BACKLOG 4
Worked on
Soon
0 Happy Jen was not so happy at all
7/18/2010 29
Unhappy Because
0 She lost touch of the products as she was more busy running to the meetings than to think about her products
0 She could never establish herself as a great product owner.
7/18/2010 30
Unhappy Because
0 Every now and then priorities would change and Jen would have to go though all the backlogs all over again
7/18/2010 31
End Result
0 The work don’t by all teams came to a standstill and a new process had to be found.
0 That led Happy Jen to a new way of thinking
7/18/2010All rights reserved Vibhu Srinivasan
32
Take 2 Minutes
0 Take two minutes – talk to you neighbor and discuss what Jen could have done differently
7/18/2010All rights reserved Vibhu Srinivasan
33
A little bit about Paul
7/18/2010 35
0 Paul was the product owner of a financial products company
0 He knew this business damn well
0 The system he set out to built had huge financially ramifications if he messed it up
How much time did he spend with the team
1000 % 7/18/2010 36
How much time did he spend with the customer
1000 % 7/18/2010 37
Paul did not know Scrum or XP.
His teams did
7/18/2010 38
Complex financial algorithms would be written in a two week
sprint
7/18/2010All rights reserved Vibhu Srinivasan
39
Guess who was often the pairing Partner
You are right
7/18/2010 40
Paul would do just in time design
7/18/2010 41
He would sit and prototype with the team
7/18/2010 42
The team could constantly question him on any feature
7/18/2010 43
There would not be a standup without Paul
7/18/2010 44
After 30 plus Sprints, the team went from a Scrum mode to
Kanban like approach
7/18/2010 45
Paul was a master of dropping features not necessary
7/18/2010 46
With Paul, the team felt the joy of doing work together and
everyone in the team was appreciated
7/18/2010 47
0 The system after many years is still in use and in great shape.
0 Paul meanwhile has gone to do other things, I am sure he has carried a few Agilish ideas with him
7/18/2010 48
To Conclude
7/18/2010 49
Your product is only as good as your product owner, choose them wisely.
0 Understand your product owner and learn to work with them closely
Thanks for listening
0 All characters in this presentation are fictional, any relation to real humans is simply coincidental
7/18/2010 50