Mastering Common Product Owner Challenges · Mastering Common Product Owner Challenges Author:...

Post on 14-Oct-2020

1 views 0 download

transcript

Mastering  CommonProduct  Owner  Challenges

Roman  Pichler

©  2010  Pichler  Consul:ng  Limited 2

Contact  Info

Roman Pichlerromanpichler.com

+44 (0) 7974 203772roman.pichler@romanpichler.com@romanpichler

Contents

©  2010  Pichler  Consul:ng  Limited 2

The  Theory

©  2010  Pichler  Consul:ng  Limited 4

The  Product  Owner

“The  Product  Owner  is  the  one  and  only  person  responsible  for  managing  the  Product  Backlog  and  ensuring  the  value  of  the  work  the  Team  performs.  This  person  maintains  the  Product  Backlog  and  ensures  that  it  is  visible  to  everyone.”

Ken  Schwaber,  Scrum  Guide

©  2010  Pichler  Consul:ng  Limited 5

The  (Rather  Harsh)  Reality

©  2010  Pichler  Consul:ng  Limited 6

The  Proxy  Product  Owner

©  2010  Pichler  Consul:ng  Limited 7

The  Underpowered  Product  Owner

©  2010  Pichler  Consul:ng  Limited 8

The  Overworked  Product  Owner

©  2010  Pichler  Consul:ng  Limited 9

The  Passive  Product  Owner

©  2010  Pichler  Consul:ng  Limited 10

The  Distant  Product  Owner

©  2010  Pichler  Consul:ng  Limited 10

The  Product  Owner  CommiLee

©  2010  Pichler  Consul:ng  Limited 11

No  Vision

©  2010  Pichler  Consul:ng  Limited 12

Wish  List  for  Santa

©  2010  Pichler  Consul:ng  Limited 13

Ice  Age  Product  Backlog

©  2010  Pichler  Consul:ng  Limited 14

Big  Bang  Release

©  2010  Pichler  Consul:ng  Limited 15

No  Release  Planning

©  2010  Pichler  Consul:ng  Limited 16

Summary

©  2010  Pichler  Consul:ng  Limited 17

To  Master  the  Challenges  …

• Ensure  every  Scrum  team  has  an  empowered,  available,  commiJed  and  qualified  product  owner

• Use  a  shared  vision  to  describe  your  overarching  goal

• Collabora:vely  groom  the  product  backlog;  weed  out  items  that  are  not  essen:al  to  bring  the  product  to  life

• Create  a  product  with  minimum  func:onality;  release  product  increments  early  and  frequently

• Carry  out  release  planning  to  guide  the  project  proac:vely;  involve  the  Scrum  team  and  the  stakeholders

©  2010  Pichler  Consul:ng  Limited 18

Famous  Last  Words

“UnUl  recently,  I  viewed  this  relaUonship  [between  product  management  and  development]  as  one  of  many  changes  in  a  Scrum  adopUon.  I  now  view  it  as  the  most  criUcal  change,  the  lynchpin  of  the  adopUon.  

If  this  change  is  successful,  the  use  of  Scrum  will  persist  and  benefits  will  increase.  If  the  change  isn’t  successful,  the  use  of  Scrum  in  your  enterprise  might  well  unravel.”

Ken  Schwaber,  The  Enterprise  and  Scrum

©  2010  Pichler  Consul:ng  Limited 19

Find  out  more:

©  2010  Pichler  Consul:ng  Limited 20