Community Blog

We've all had challenges with various stakeholders coming to us with a whole bunch of different information and wanting a whole bunch of different things. Who do I listen to? What’s most important?

Scrum e il principio di unicità risponde ad una domanda che capita spesso in formazione: come usare Scrum per un team di più di 11 persone?

In my live training, I often ask students why we estimate. The answer I usually hear is some version of...“So we know how big something is and how long it will take.”  

One of my customers is asking me about the accountabilities of a Product Owner and how they break down.

So in this week's vlog we will continue our discussion from last week's vlog and also about a subtle change in Scrum Guide which I think is quite powerful when done right in our organisation.

Have you ever noticed people keep talking about things, but they've not aligned with what their words mean? I have seen agility measured as the number of "agile teams" and the "number of training attendees" more often than I like to admit.

When (Patricia Kong - Product Owner of Enterprise Solutions at Scrum.org) taught me how to combine the chocolatey-goodness of Evidence Based Management with the hazelnutty-goodness of Hypothesis Driven Delivery, I was ecstatic! "AHA!", I says to myself.

Sind mehrere Product Owner nötig, um Scrum effektiv zu skalieren? Nein.  Dass in skalierter Produktentwicklung mehrere Product Owner von Nöten sind, ist ein weit verbreiteter Irrglaube. Dieser Beitrag räumt mit diesem Irrglauben auf. Wird die Product Owner Rolle durch mehrere Personen skaliert, führt es zu Wertminimierung, steigendem Risiko und unnötiger Verlängerung der Time to Market. Es ist somit eine ineffektive Art, Product Ownership zu skalieren.

On today's episode of YOUR DAILY SCRUM: Can one person be both the Scrum Master and Product Owner on a Scrum Team?

In the The Evidence-Based Management Guide we talk about the Intermediate Strategic Goal and I likened that to the Product Goal in the 2020 Scrum Guide.

The Scrum Accountability Game is an interactive and fun game that you can play with others to reimagine the accountabilities in Scrum. Compatible with the new Scrum Guide 2020. Have fun! #scrumon

Brief about me before you read this post so you can understand my perspective better. I am a software developer and Scrum Teacher...

What are the Scrum Product Owner's Accountabilities & Responsibilities? Are they just Business Analysts who detailed User Stories in JIRA?

What is up awesome people? I hope you are having a great weekend.

In today's vlog I discuss five indicators to identify whether someone is the Product Owner.

In May 2019, I spoke at the Agile Manchester conference, where I presented my talk "The Product Owner's Toolbox".

Lors de mes formations Scrum

Starting from today, I am going to start a new series on my channel which I will call the 2 minutes FAQ series.

I've been using a visualization that people find useful for understanding the relationship between the various Lean/Agile requirement containers. Some people call the full model a dinosaur. Others are reminded of the snake who ate an elephant from "The Little Prince". (I'm sure there is a good connection to elephant carpaccio somewhere in here ...). In this article I'll explore this model and connect it to the stances of the Scrum Product Owner. 

What's up awesome people. I hope you are all having a great week.

Would like a tool that delivers better product and customer outcomes and actually pays for itself? Read on.

How much have you scored this year? My parents asked this question twice a year throughout my schooling. I was well prepared to ask the same questions to my son, but school cheated me. Have you had a similar past? If yes, then you will understand why I call it a generation gap issue.

Like other PSTs, I was recently approached by few agilists to help them with PSPO-I certification. Here is one such conversation -

What is a Product Owner? What are the differences between a Product Owner and Project Manager? Isn’t a Product Owner some kind of an Agile Project Manager? These are some of the questions we often get from people in our Scrum.org classes.

A question that frequently comes up in my Scrum Training courses is how to define a product.

When we talk about Scrum for complex Product Development, it starts from Vision and Product Backlog.

In my daily life as a Scrum Master, I witness many crazy situations. I want to share my discoveries via this comic series featuring Koos Coach, the silly Scrum Master struggling to understand and master Scrum.

I've learned and experienced that most symptoms can be traced back to not adhering to the Scrum Roles. Let's start with the Product Owner role.

Often, when I facilitate a Professional Scrum Training, I'm asked about how a Scrum Team can work without someone telling them what to do.

The Professional Scrum Master (PSM) workshop has a module that talks about the Definition of "Done" (DoD) and Technical Debt.

The Clerk is your personal waiter for all your user story serving. Gathering all the wishes, user stories and demands is what The Clerk does.

Some of the most famous and influential leaders of all times include people like Mohandas K. Gandhi, Nelson Mandela, Martin Luther King Jr. and Abraham Lincoln.

The Project Manager is typically concerned with day-to-day progress of the Development Team.

The Customer Representative Product Owner is the go-to person for people in the organization who want to gain a understanding of what customers (and/or users) are looking for in the product or service which the Product Owner is responsible for.

Visionary Product Owners are people like Steve Jobs, Elon Musk, Thomas Edison and Winston Churchill.

In this vlog, I also share some of my observations on how companies structure the relationship between Product Owner and Product Manager in a scaled Scrum environment.

A User Story is the most widely used Agile Practice for capturing needs and requirements and describing Product Backlog Items. To get the most of any technique it is good to understand the why behind it not just the what. Let’s discuss how to write better User Stories in Scrum.

Warning - this post is not about Scrum. It is about Technical Debt in my home!!! Please do not judge me!!

Product Owners have a tough job. I was in a Sprint Review recently where the Scrum Team had some stakeholders talking about an idea they thought was excellent. So, like any studious Product Owner, they immediately typed up the idea and added it to their Product Backlog.

This is a common question in my Professional Scrum classes. The topic of combining Scrum roles often comes up early when we are still learning the basics of the Scrum framework.  It comes up because people are already wearing two hats or are being told that they will be.

Getting your thoughts down on paper is a great way to reflect on and sort out the complicated aspects of our industry. The three Vs of Product Ownership is an example of this and is a major theme of our book — and the topic of this post.

In this blog, PSTs Sjoerd Kranendonk and Wilbert Seele explain how to achieve more and risk less by being a less visible Product Owner. In the Scrum Guide the following is written about the role of the PO: "The Product Owner is responsible for maximizing the value of the product and the work of the Development Team."