The perfect Product Owners flow

The perfect Product Owners flow

Since my first projects when I started experimenting with extreme programming and Scrum I am intrigued by the importance of the Product Owner role and the lack of support to be found.

So I started to search for tools and techniques which could support PO's in their work so we all would benefit and start delivering these kick-ass products. My journey started from within the processes (Scrum and Xp practices) and expanded over the years more and more to the business side of things.

More recently I started to experiment with a thing I call the feedback model. This means that there needs to be a continuous validation cycle of objectives against outcomes: are our goals reached through the new features or changes in the product?

(Hylke Stapersma and me even created an open source business goal validation framework called Gareth. More on the Business goal validation is to be found here)

The result, which will still evolve more, is what I call a typical product flow (or more as the clickbait like title states: the perfect Product Owners flow):

The model is designed as a flow from the strategy, business, operational and the feedback models. The flow consists of two important feedback cycles:

– Driven by objectives and validated by outcomes.

– Organized by input and measured by output.

In a greenfield situation you'll start on the left and work your way to the right. Then you go back to the left again and verify all parts again with the knowledge you gained by gathering feedback from the behaviour of your users. If you are in an existing environment you can do what I did. You just have to get you shop in order first. You start in the middle and work your way to the left. From there you can follow the flow just like with a greenfield situation.

None of the artifacts in the flow should ever be static! Them being static means that there has been no validation.

If you would like to more don't hesitate to get in touch. I can also provide a workshop based on this flow: https://nielstalens.nl/trainings/product-owner-workshop/

Niels Talens

Product Owner Engineering Workplace

6 年
回复
Hijmen Schilperoort

Product Owner Scanning & Archiving bij Nationale-Nederlanden

6 年

when do we start Niels?

回复
Doralin Duta

a.i. Scrum Master/Coach

6 年

Where would you embed the (Service) Design Thinking in your flow?

回复
Imad Essadeq

Geen excuses, alleen oplossingen | Founder TestBotics | Automatisering | AI | Kwaliteit als fundering

6 年

Cool!

要查看或添加评论,请登录

Niels Talens的更多文章

  • Product denken stap 1: strategische doelen

    Product denken stap 1: strategische doelen

    In de praktijk zie je dat het vaak lastig is om de relatie tussen de strategische doelen en producten te herleiden. Wat…

  • Waardegedreven product denken

    Waardegedreven product denken

    Bij productleiderschap gaat het niet zozeer om voortgang op features, maar of veranderingen het gewenste effect hebben…

    1 条评论
  • Value driven product thinking

    Value driven product thinking

    Product leadership is not so much about progress on features, but whether changes have the desired effect on achieving…

    1 条评论
  • The monkey trap

    The monkey trap

    There is a story about some kind of monkey trap that was once used in India. There would be a hollow coconut with a…

    3 条评论
  • Platform teams as driving force of improvement

    Platform teams as driving force of improvement

    What is a platform There are many types of platforms. In this series we talk about a platform as a group of…

  • The importance of splitting teams (and how to)

    The importance of splitting teams (and how to)

    You could say that I am a notorious team splitter. A fiery divider of teams, wherever I go teams end up separated.

    3 条评论
  • Can you even DevOps?

    Can you even DevOps?

    You might have heard the term DevOps mentioned or even work with teams that are DevOps teams. Sometimes people say they…

    1 条评论
  • Practical shopkeeping tools for IT Management

    Practical shopkeeping tools for IT Management

    IT should always serve business goals. To be able to do just that we have to make sure we provide the right solutions…

  • Why DevOps?

    Why DevOps?

    There can be many positive effects of organising as a DevOps organisation. If you look at companies that are further in…

  • ITSM or DevOps? You don't have to choose!

    ITSM or DevOps? You don't have to choose!

    I often get questions whether an organisation should choose ITIL or DevOps. Or people tell me that 'before DevOps…

    3 条评论

社区洞察

其他会员也浏览了