Robin Dymond: Booting up Customers to Build Great Products

Who am I? 
  Robin Dymond, CST 
  Managing Partner Innovel LLC 
  21 years in software development 
  9 yrs doing Scrum + XP, 5 yrs applying Lean 
  Agile Program Coach in the largest Agile 
transition in Banking 
  Trained 2000+ people in Scrum 
  Clients in US, Europe, Canada, Brazil 

©2011 Innovel LLC. All rights reserved www.innovel.net

Just read this… 


They asked me to work with you… 


… hello….? 
….hello….? 


What can you do about this? 


How to Boot up Your 
Product Owner 

  People 
  Process 
  Tools 


Do you have the right 
person as PO? 
People over process 


Get the right person for 
the job 


Key Product Owner 
Attributes 
  A subject matter expert 
  Knowledgeable about the business 
  Has decision making authority 
  Has lots of time for the team 
  Good communicator 
  Uses the system being developed 
  Facilitates stakeholder input 
  Listens to the team 
  Understands the key role of a Product Owner in Scrum 
  Helps the team improve 

Set your relationship up 
for success 


Establish expectations 
with both sides 


Don’t expect perfection 


Send them to Product Owner 
training 


Process: 
Managing Product Owner work 


Relationships, 
Requirements, Results  

Stakeholders  What we are  Business 
and Team  building  results 


Relationships 

Stake‐ •  Customers 
holders  •  Politics 

Scrum  •  System health 
Team  •  Motivation 

Pulling features from 
the Backlog 
Ready for   Priority 
next iteration 
Team 
Next 2‐3 Iterations, 
Less deﬁned 

Epic Story 

A group of stories that 
Comprise a capability 

Epic Story 


Just In Time Backlog Grooming 

Priority 
PO and Team 

PO and Team or Analyst 

PO and other POs 


Add regular stakeholder and 
team PBL review meetings 
Product Backlog
Product 
Backlog 

Stakeholder Backlog Team Backlog NO SURPRISES
Review meeting Review meeting
Sprint planning
or Sprint review

Sprint 1 
Backlog 

Week 1  Week 2  Week 3  Repeat 

Sprint  Daily  Sprint Review, 
Planning  Standup  Retrospective 
meeting 


Define a “ready to develop” 
state for User stories to enter 
sprint planning. 


Reduce the PO Work in 
Progress (WIP) 
  How much stuﬀ is the P.O. working on? 
  What other projects do they have? 
  Whay other jobs do they have? 
  What does sales and marketing demand from 
them? Road maps? New plans, priorities?  
  How often do they meet with stakeholders? 
  How often do they work with the team? 


Visualize their work 

Write  Product  Meet with 
Whitepaper  Photoshoot  stakeholders 

Customer  2012 Marketing  Trade show 
meeting  planning  planning 

Meet with 
Update Product  Regulatory 
other Product 
Road map  update 
managers 

Review 
Prepare for  Review test 
completed User 
next iteration  plan with QA 
stories 


Reduce work in process 
Product Owner Personal Kanban
Work CUE Next WIP 2 Done
Customer 
Bla bla  Customer  More stuff 
stuff 
stuff 
Blabla  PBL  work 

Blabla  Sales stuff  Fun work 
Sales stuff 
stuff  Boring work 

More stuff  Blabla 

work 

Fun work 

Boring work 

Blabla 

Other work 

Bbsit sales 
©2011 Innovel LLC. All rights reserved www.innovel.net 
Focus group

Visualize Backlog Prep 
Kanban for Backlog Preparation

Product Ready for Ready for
Backlog Next Epics 2 User Stories team review 5 sprint planning
Bla bla  Epic 3  Story 2.1  Story 1.3  Story 1.1 
Epic 1  
Blabla  Epic 4  Story 2.2 
Story 1.4  Story 1.2 
Blabla  Epic 5  Epic 2 

stuﬀ  Story 2.3 
Story 2.4 
More stuﬀ 
Story 2.5 
work 

Fun work 

Boring work 
Limited Work In Progress


Online kanban for off 
site P.O. 


Product Ownership: scope 
creation or scope management? 


Ensuring what gets built 
delivers value 


Product Management with Fast 
Feedback 
Revise product
direction based
on market feedback
Plan product Release every Sprint  Check
increments, Market
Market tests response


Is what we built being used? 


Automate market feedback, 
make it transparent 


Your Product Owner needs 
a process too 
  Scrum is silent on how product owners should 
manage their work 
  Product Owners feed the rest of the 
development system and are a constraint 
  Find ways to build and support eﬀective work 
processes for your POs. 
  Deﬁne what “Ready for development” means 
for user stories 
  Use Lean and just in time ideas to eliminate 
overworked POs 

Perfection is a journey… 


Thanks Steve. 


Questions? 


Innovel LLC  
Training and Consulting in 
Scrum XP Agile Lean Kanban 
Robin Dymond, CST 
rdymond@innovel.net 
www.innovel.net 
www.scrumtraining.com 
Americas: (804) 239‐4329 
Europe: +32 489 674 366

Robin Dymond: Booting up Customers to Build Great Products

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (13)

Semelhante a Robin Dymond: Booting up Customers to Build Great Products

Semelhante a Robin Dymond: Booting up Customers to Build Great Products (20)

Mais de Agile Lietuva

Mais de Agile Lietuva (20)

Último

Último (20)

Robin Dymond: Booting up Customers to Build Great Products