Double O Model – How a Product Owner can escape the hungry Beast Scrum

As Richard Stinear mentioned  recently  „Scrum is a hungry Beast, that wants to be feed constantly by Product owner“. Lets see how Product Owner could escape this end-less-loop.

Gabrielle Benefield recently published by Twitter the Double O Model (see graph below). As I understood it will be part of her new Book, that comes out soon🙂. It shows the 2 O’s, where on the left hand side Product Owner is creating new Options and Innovations that will bring valuable Outcome. On the other side we see the delivery cycle, that runs experiments with common Output like Stories, Bugfixes, etc. Those impact are measured/adapted and flow back to Create Options O.

BWH1fK3CYAAtvQ4.png-large

By Alistair Cockburn @TotherAlistair

What is danger now if a Product Owner is fully occupied in the delivery O, without any time left for Innovation.

Some Product Owners are captured in delivering Output, instead of caring about valuable Outcome

Gabrielle Benefield, 10/2013

In other Words Team and Product Owner are just focused to deliver fast, but wrong, non-valuable Output. To get back to the left O it’s recommended to constantly do a  critical review of your current top Backlog Items and check there Outcome. As Alternativ go back to your stakeholders, the team and ask for the 2 most valuable Requests each and try to calculate the costs if Item wont be Done.

Mirko Kleiner is a Blogger, Agilist (Agile Evangelist), Vice President Delivery at youngculture AG, Twitterer, Father of 2 beautyful Sons and Partner of a lovely Wife.

Tagged with: , , , , , , , , , ,
Veröffentlicht in field experience, scrum
2 comments on “Double O Model – How a Product Owner can escape the hungry Beast Scrum
  1. Hans-Peter Korn sagt:

    Interessant! Auch hier wieder ein wenig zurück zum „zuerst Denken und Überlegen – dann erst Handeln“ welches bei radikalen Agilisten ja als „wasserfallig“ verpönt war….
    Siehe dazu auch slide 11 von Alistair Cockburn in http://pionierbasis.us2.list-manage2.com/track/click?u=fad3f7c7d7e05b52e71519483&id=03b7485044&e=e78b3f1053 als weiterer Hinweis zum „vorher Denken“…

  2. mirkokleiner sagt:

    Genau, wobei das Probieren z.T. auch nicht fehlen darf. Dann aber bitte mit konsequentem Mesure & Adapt.

Schreibe einen Kommentar

Trage deine Daten unten ein oder klicke ein Icon um dich einzuloggen:

WordPress.com-Logo

Du kommentierst mit Deinem WordPress.com-Konto. Abmelden / Ändern )

Twitter-Bild

Du kommentierst mit Deinem Twitter-Konto. Abmelden / Ändern )

Facebook-Foto

Du kommentierst mit Deinem Facebook-Konto. Abmelden / Ändern )

Google+ Foto

Du kommentierst mit Deinem Google+-Konto. Abmelden / Ändern )

Verbinde mit %s

mirkokleiner

mirkokleiner

Mirko Kleiner is a Blogger, Agilist (Agile Evangelist), Vice President Delivery at youngculture AG, Twitterer, Father of 2 beautyful Sons and Partner of a lovely Wife.

Verifizierte Dienste

Vollständiges Profil anzeigen →

  • When you blame others you give up your power to change. Take responsibility for your future! - Chris Voss #quote 9 hours ago
  • Let us never negotiate out of fear. But let us never fear to negotiate. - John F. Kennedy #quote 12 hours ago
  • Success is the result of good judgement, which is the result of experience, experience is often the result of bad judgement. - Tony Robbins 1 day ago
  • RT @BillGates: Anybody can learn to code. And everyone should give it a try: b-gat.es/2h3cAzd #HourOfCode 1 day ago
  • Do what you can, with what you have, where you are. - Theodore Roosevelt #quote 1 day ago
%d Bloggern gefällt das: