Community Blog

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

Many teams are struggling with delivering modern software because they are not building with Test First Principles. Test First gives us the assurance that we have built the correct thing, that what we built is what the customer asked for and that when we change things we don’t break anything inadvertently.

"How do you get an inexperienced Product Owner to concentrate on the why's and the value delivered by a feature/requirement, rather than a list of what's e.g we must gather a,b,c... x,y,z info from our users"

Together with my colleagues Uwe Schirmer and Kurt Bittner, I have compiled a book that contains many of our own stories and those we experienced while working with customers and students: The Professional Scrum Team. Maybe they provide value to you. 

Four PST's (Andy Hiles, Steve Trapps, Sjoerd Kranendonk and Jasper Alblas) discuss the changes in the 2020 version of the Scrum Guide. You can watch the video above.

On November 18, 2020, Ken Schwaber and Jeff Sutherland released an updated version of the Scrum Guide. In this blog post, I will share what you need to know about the 2020 Scrum Guide.

The following are the changes that struck me the most in the 2020 Scrum Guide...

In the 2020 Scrum Guide, the Definition of Done is created by the Scrum Team. In previous versions of the Scrum Guide, this responsibility was explicitly owned by the Development Team. I will explain the intention of the change and what it means for Scrum Teams.

In the 2020 Version of the Scrum Guide, the commitments were introduced for each artifact. These then became an element of Scrum; in that they need to be used to gain the maximum value that the Scrum Framework offers. They were always part of a Professional Scrum approach, now there is a clear connection of these commitments to the artifacts. They increase transparency, and the focussed delivery of Value. Each of the commitments now clearly support and sustain an artifact.

Scrum Guide 2020 Poster After yesterday's Scrum Guide 2020 launch event by Ken and Jeff, I am excited to announce the release of the new Scrum 2020 poster.

Professional Scrum Trainer, Sahin Guvenilir, discusses measuring value, improving outcomes, and using the best available evidence to decide the next steps against a Strategic Goal.

Heute, am 18. November 2020, pünktlich zum 25. Geburtstag von Scrum, haben Ken Schwaber und Jeff Sutherland den Scrum Guide aktualisiert.  Um eines gleich vorwegzunehmen: Scrum bleibt Scrum. Ein einfaches Rahmenwerk, welches es Teams ermöglicht, mit der Arbeit an komplexen Problemen zu beginnen. Und der Scrum Guide 2020 ändert daran nichts.  Einige Dinge sind jedoch neu und denen widmen wir uns jetzt. 

Doing Scrum is not enough! The precious result will not be achieved just by understanding and following the rules and principles of the Scrum Framework. Every day organisations are starting and failing with business agility, praise and blame Scrum.

Une Sprint Rétrospective est une opportunité, pour l'équipe Scrum, d'inspecter le déroulement du Sprint et créer un plan d'amélioration à adopter lors du prochain Sprint.

La Sprint Review est l'événement au cours duquel l'Équipe Scrum et les parties prenantes (invitées par le Product Owner) se retrouvent pour inspecter l'Incrément et adapter le Product Backlog.

Le Daily Scrum est un évènement quotidien destiné à l'Équipe de Développement et qui a pour but de planifier le travail des prochaines 24 heures. C'est un time-box de 15 minutes.

El compromiso del equipo de desarrollo durante el Sprint es lograr el Sprint Goal y con ello el impacto en los clientes y en el negocio. El éxito del Sprint está asociado al logro de este objetivo y a los cambios en el comportamiento de los clientes que se puede provocar con el uso del producto.

The Sprint Review is not just a "Demo" or a presentation, it is a collaboration of the Scrum Team with the stakeholders from the business.

Scrum Master aufgepasst! Der Sprint beginnt nach dem Sprint Planning. Handelt es sich hierbei um einen Scrum Mythos oder Fakt?

Le Sprint Planning est le premier évènement d'un Sprint. Son objectif est de collaborer à la planification du travail à effectuer durant le Sprint.

Was denkst Du, handelt es sich hierbei um einen Mythos oder um einen Fakt? Die Antwort erfährst Du in meinem Scrum Mythen und Fakten Check.

Scrum prescrit cinq événements, le Sprint en est le coeur et le conteneur de tous les autres. Il a une durée d'au maximum un mois, ou moins, au cours de laquelle un Incrément de produit...

L'équipe Scrum est auto-organisée et pluridisciplinaire. Elle est composée de trois rôles avec des responsabilités clairement définies :

When I first became a Scrum Master, I heard the phrase assume positive intent over and over again. And it really resonated with me.

Pour bien comprendre les fondations de Scrum, nous partons du postulat que nous créons et maintenons des systèmes complexes : un système informa

Scrum est un cadre de travail dans lequel les personnes peuvent résoudre des problèmes adaptatifs complexes, tout en fournissant de manière productive et créative des

"Scrum and Organizational Design in practice" is my contribution to 

It’s interesting how we sometimes accept some rules without questioning them at all, and how some other times we try to bend them to suit our needs.

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.

Executives: there are many reasons for agility. You already know this.

Scrum is a straightforward framework to develop complex software products in a complex environment but hard to practice.

Scrum Master's role is unique, and comparing with any traditional roles will limit our thinking and exploring a beautiful journey of servant leadership.

A few weeks ago, I had a wonderful conversation with Diana Larsen on Agile FM, and it did not come as a surprise, that the topic of retrospectives came up. Diana is the co-author of the book Agile Retrospectives , which has been very influential in many agile careers, including mine. 

As an active agile Scrum Consultant and Professional Scrum Trainer, I am constantly helping a large number of agile teams. Unsurprisingly all the teams I am supporting are experimenting with different ways to make remote working, work!

Chacun d’entre nous à eu un déclic concernant Scrum, nous avons compris que c’était la route à emprunter, un comportement que nous souhaitions adopter, des valeurs alignées avec les nôtres.

Having a Sprint Goal in some cases is not easy. Having a good Sprint Goal is even more difficult.

Every Sprint starts with a Sprint Planning event. It is very crucial to ensure that the Scrum Team comes to a shared understanding of what and how are they going to deliver a “Done” increment that creates maximum business impact.

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.

The Scrum Team gathers around their team desk to hold the Daily Scrum.

In this blog, we’ll dive deeper into the topic: “Scrum Master vs Project Manager”. If you’re having a similar question about the Product Owner vs the Project Manager.

One of the teams I worked with suggested dropping the Sprint Retrospective and the Sprint Review from the Sprint and only do them every other Sprint.  

Earlier this year, I released the complimentary Scrum Poster with the goal to give Scrum Teams around the world a medium to see the Scrum Guide in visual form.

Recently I ran into a beautiful piece of text, written by Rachel Naomi Remin. In this text I read the following phrase:"Perhaps the secret of living well is not in having all the answers, but in pursuing unanswerable questions in good company"

The other day, I picked up my son from soccer and he had a huge smile on his face. I asked him how it was and he answered with an even bigger smile “Awesome!”.

Earlier this year, we had released the complimentary Scrum Poster and the response was way beyond positive. We love that teams around the world use the poster to make Scrum transparent.

Somewhere between the CEO and 1st line management level, "you do Scrum, just get it done, how much money you need, and what kind of people you need."  "It's just another framework." Salespeople were saying, "you're doing Scrum magic and making it faster." Sometimes people don't want to change.

Katas and patterns go hand in hand and so does the Agile Transformation Kata (ATK) harmonize very well with the organizational change patterns published for example by Mary Lynn Manns and Linda Rising in their book  More Fearless Change.

I often wonder about the Trustpilot reviews straight after a workshop. Did I entertain? Did I perform? Were attendees satisfied? Are attendees inspired? It matters. I just think it matters more if the workshop made a difference to the work lives of attendees. I can't take credit. The client does the hard yards.

In my Professional Scrum classes, I always get asked about best practices.  It may be about facilitating events, Product Backlog refinement, defining value, forming Scrum Teams, or creating good Sprint Goals.