Willem-Jan Ageling: The task-centric, command-and-control PO and its consequences on the Scrum team

The amount of time a Product Owner spends thinking and working on the details is one of the aspects that has the biggest impact on the team. In this episode, we talk about two contrasting PO approaches: from the high-level focus of the Sprint Goal to the task-centric, command-and-control PO.

The Great Product Owner: Crystalizing the Sprint Goal

When we help teams, and Product Owners focus on the User Stories, we are helping them understand, and follow-up on the items they should work on. However, when we help the Product Owner and the team focus on the Sprint Goal, we are helping them focus on impact and outcomes over the tasks and stories they need to work on. This enables many positive behaviors, and when you find a PO that is able to crystalize a Sprint in a Sprint Goal, you know you’ve got gold in your hands, you’ve got a great Product Owner!

The Bad Product Owner: The task-centric, command-and-control PO

Sometimes, Product Owners behave as if they were Project Managers. When that happens, there’s many patterns that emerge in the team, and int he PO-team collaboration which Scrum Masters must actively manage, or mitigate. In this episode, we talk about the task-centric, command-and-control PO, and what you can do to help the PO and team find a better way to collaborate.


Are you having trouble helping the team working well with their Product Owner? We’ve put together a course to help you work on the collaboration team-product owner. You can find it at: bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO’s collaborate.

About Willem-Jan Ageling

As a Scrum Master and writer for Serious Scrum, Willem-Jan is passionate about helping people understand what it means to work in a complex Product Environment. Which is how he likes to talk about Scrum.

You can link with Willem-Jan Ageling on LinkedIn and connect with Willem-Jan Ageling on Twitter.

Leave a Reply

Your email address will not be published. Required fields are marked *