The reasons Scrum Masters violate the spirit of the Scrum Guide are multi-faceted. Typical Scrum Master anti-patterns run from ill-suited personal traits to complacency to pursuing individual agendas to frustration with the team itself.

First, in a blog series about the upcoming book:

In Scrum, part of the Product Owner accountability is to provide a forecast that sheds light on possible answers to the when will we get there question. In my last post, we discussed three ways to size Product Backlog items (PBIs). Today, we’ll discuss ways the Product Owner can use this information to create a meaningful forecast.

Three simple retrospective formats based on the Liberating Structures "Conversation Cafe", "Troika Consulting", and "Discovery & Action Dialogue"

Scrum ist ein taktisches Framework für die Entwicklung von Produkten, vorausgesetzt, Sie erkennen im Voraus, was es wert ist, entwickelt zu werden. Aber selbst nach einer erfolgreichen Produktentdeckungsphase, neudeutsch: Product Discovery, kann es Ihnen schwer fallen, das Richtige auf die Beine zu stellen, wenn Ihr Product Backlog der Aufgabe nicht gewachsen ist: Garbage in, Garbage out. Der folgende Artikel zeigt 27 gängige Product Backlog Anti-Patterns — auch für den Produktbacklog-Verfeinerungsprozesses — auf, die den Erfolg Ihres Scrum-Teams beschränken.

When you aspire to a Scrum Master role, some form of certification on your resume is a must. Scrum.org offers the acclaimed PSM learning journey to support Scrum Masters to professionalise their skills. I am a Professional Scrum Trainer for scrum.org and I have trained hundreds of Scrum Masters over the past few years.  Newcomers start their career with a PSM-I class to gain an understanding of Professional Scrum and the essence of the role of the Scrum Master. I observe that many experienced Scrum Masters hesitate to join a PSM-II class. Possibly that's because it is unclear to many what the PSM-II training has to offer.

When will we get there?  It’s not just something you might hear from the back seat of a car on a long road trip.  It’s something that a Scrum Team’s stakeholders, customers, managers and many others want to know.  When will that thing you are working on be done?  How long do I have to wait for you to deliver what I want? Sound familiar? Today, we’re going to discuss three ways to estimate and in my next post, we’ll talk about forecasting.

Scrum is a tactical framework to build products, provided you identify what is worth making in advance. But even after a successful product discovery phase, you may struggle to create the right thing in the right way if your Product Backlog is not up to the job—garbage in, garbage out.

Was haben eine Agile Transformation, die Dienstleistung einer Personalabteilung und ein Softwareprodukt gemeinsam?

Imagine the stress of getting to work and observing your heart rate rising. It feels as if everyone is out for blood, anything you say can be used against you no matter how genuine it may seem-and managers don't really know what's going on either; they've got favourites among their team members who make most decisions behind closed doors with just a few people involved in each one (those "in the know").

This blog talks about Integrating UX with Scrum.

Hoy me vengo arriba un poco. Vengo a comentar que competencias creo que tendría que tener un líder agile.

In 2020 the Scrum Guide introduced the classification of three commitments -

When I coach, consult and teach classes, I often get questions about creating an agile maturity tool or defining agile maturity metrics. Agile Maturity metrics are used by many businesses to better understand their present agile practices and monitor to improve them. I understand the need for this kind of metric. I also noticed that the purpose and value of agile maturity metrics are misunderstood. This article will help you to find agile maturity metrics that bring value and offers a free maturity tool to download.

An investigation of three schools of thought on team development and high-performing teams

In dieser spannenden 38. Hands-on Agile-Session ging Roman Pichler auf eure Fragen zur Product Owner Rolle ein. Die Themen reichen von Produktmanager vs. Product Owner vs. Business Analyst über die richtige Größe des Product Backlogs bis hin zur Verknüpfung von Produktvision und Product Goal und Sprint Goal.

Scrum es un marco de trabajo con un cambio cultural, usar solamente la parte visible ignorando la parte cultural que se basa en los principios y valores pueden llevar a no usar Scrum adecuadamente y no aprovechar sus beneficios.

Some years ago, I was working with a team developing a new product at a technology company.  The team was concerned that their Time to Market (T2M) was too slow, and they believed that they would be able to improve it by automating their build-and-test process. Automating any manual process is usually a good investment to improve T2M, but I suggested that we should first look at their overall T2M using a very simplified value stream map to understand where they were spending their time. 

If you are a Star Wars fan like me, then you know that Star Wars is more than a story; it’s an Epic which holds many important life lessons.  Below are the top five things I learned about Scrum from Star Wars.

How to support Scrum Teams to effectively bridge the gap between their current and desired state

In this energizing 38th Hands-on Agile session, Roman Pichler delved into your questions on the role of the Product Owner. The topics range from product manager vs. Product Owner vs.

Die neue Art, im digitalen Zeitalter über Produktmanagement nachzudenken, besteht darin, das Produkt als eine Data-Mining-Maschine zu sehen.

Me cuesta mucho imaginarme una capacitación sin que algun participante me pregunte por la daily. 

Agile implementations shift culture, yet many organizations limit themselves to the bare minimal execution of a framework and call that Agile.

To date, less than 1500 people have passed the Scrum.org PSM III or PSPO III assessments and gained the associated certifications. This has always struck me as a low number. The post will explore why that might be, why the number should not be so low and why you might want to consider gaining one of these advanced certifications.

Quando si cerca di prevedere il futuro, si è raramente nel giusto. Le stime probabilistiche aiutano a migliorare le previsioni di uno Scrum Team.

Immer wieder habe ich es erlebt: Scrum Teams arbeiten an mehreren Produkten parallel. Erstmal sei gesagt, dass es enorm stressig für die meisten Mitarbeiter:innen ist an mehreren "Baustellen"  gleichzeitig zu arbeiten.

Willkommen zum Sprint Anti-Patterns-Artikel aus unserer Serie über Scrum-Anti-Patterns. Ich adressiere in diesem Artikel sprintbezogene Fehlverhalten der drei Scrum-Rollen, der Stakeholder bzw. Interessenvertreter sowie des IT-Management.

Produktentwicklung ist komplex. Scrum Master sind Manager dieser Komplexität.

What is an Increment and how does it connect with the other elements of Scrum?

Try this experiment and go on a journey to find your real stakeholders!

​​​​​​​The concept of iterative, incremental Product delivery is included in the Scrum Guide.  But did you know that the Agile Manifesto refers to incremental, iterative delivery in at least 3 of the principles?   

TL; DR: 28+2 Sprint Anti-Patterns from Sprint Stuffing to Gold-Plating Welcome to the Sprint anti-patterns article from my series on Scrum anti-patterns, covering the three Scrum roles—pardon me: accountabilities—and addressing the contributi

Recently I had an epiphany, realising that most of my writing has been for Product Owners and how to they should interact with the environment, but what about how to interact with Product Owners? What are some characteristics and traits you may encounter as a stakeholder, manager or leader of a Product Owner.

Wenn dein Team auch Probleme damit hat, gute Sprint-Ziele zu formulieren, dann lass mich dir mein Rezept geben. Es wird dir eine Menge Zeit ersparen.

Me he encontrado muchísimas organizaciones que lo primero que quieren hacer la agilidad de lo grande. En lo primero que piensan es en cambiar enteras. Si somos 5000, vamos a hacer un plan para cambiar los 5000. Y Roma no se hizo en un día. Se fue construyendo con el tiempo.

Nach meiner Erfahrung ist das Daily Scrum das Scrum-Ereignis mit der höchsten Anti-Pattern-Dichte unter allen Ereignissen. Erfahren Sie mehr über die Daily Scrum Anti-Patterns, die Ihren Weg zur Agilität gefährden.

Un producto tiene un sólo Product Backlog y es gestionado solamente por un único Product Owner. El Product Owner es responsable de la visión, aclaración, ordenamiento del Product Backlog y valor final que proporciona el producto o servicio. Este Product Owner puede recibir ayuda de los Desarrolladore y tener a otras personas que le ayuden a una mayor descomposición del Product Backlog o en la identificación de las dependencias. Al escalar Scrum, pueden existir muchos equipos Scrum, pero aun así existe un único Product Owner para el producto.

Professionalism is a key part of our identity at Scrum.org. We spend a lot of time thinking about how to bring professionalism alive for our learners, our trainers and the broader community.

Recently I was asked to answer some questions for a journalist on how to structure IT organizations. The questions were interesting and I wanted to share my responses here.

In this blog post we will give examples of Increments and why it is important to have Done Increments

Teams that change the framework are not using Scrum and are missing out on some of its benefits.  The Scrum framework consists of 5 events, 3 accountabilities, 3 artifacts and five values.  Today, we will talk about the order of the events in Scrum. 

TL; DR: 24+2 Daily Scrum Anti-Patterns In my experience, the Daily Scrum is the Scrum event with the highest anti-pattern density among all events.

Bei der Skalierung von Scrum balancieren wir Kosten und Aufwand mit Nutzen und Vorteilen. Kosten und Aufwand werden durch zusätzliche Teams verursacht. Nutzen und Vorteile entstehen dadurch, mehr potentiellen Wert in gleicher Zeit zu liefern.

The new Scrum Guide 2020 mentions Scrum is founded on empiricism and lean thinking. In this post, Anand Pandey dives into how to identify waste.

What's up awesome people? I hope you are well and keeping safe. I have been asked many times recently about the career paths for Scrum Master. I personally think Scrum Master should not be a job title. But what does that mean to Scrum Master career path if Scrum Master is not a job title ... I think it creates lots of doors of possibilities. In today's podcast episode I share four possibilities for Scrum Master career paths. Hopefully it also inspire those of you in the Human Resources or People Operations department to redesign not only career paths for Scrum Master but also career path at your company in general. Enjoy the podcast and have a great week ahead folks.

A detailed description of how the Scrum Master role embodies 6 stances, and why I don’t consider “servant leader” and “manager” valid stances anymore

Hoy he venido profundo y filosófico. Siempre en mis formaciones comento la diferencia entre ordenar y priorizar.

Professional Teaching is a complex skill that requires practitioners to probe, sense and respond to a changing learning environment. As Scrum Masters, we are naturally at home within complexity, and therefore the ability to apply empiricism to learning should be simple.

In Scrum soll ein verwendbares Increment und in Design Thinking sollen nur Prototypen erstellt werden. Wie kann das trotzdem zusammen passen?