Community Blog

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.

Scrum Values make the use of Scrum successful. How can the Scrum Master use these to grow trust within the team even more? Check it out!

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.

We are unique because we can choose to detach ourselves from hardwired biological goals. 

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.

Scrum Values make the use of Scrum successful. How can the Developers use these to grow trust within the team even more? Check it out!

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. 

In Kürze: 24+2 Daily Scrum Anti-Patterns Nach meiner Erfahrung ist das Daily Scrum das Scrum-Ereignis mit der höchsten Anti-Pattern-Dichte unter allen Ereignissen.

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.

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.

Prior to reading this blog, please read the introduction to this series he

How the Agile Kata can help following through on Improvement ideas, identified for example in a Sprint Retrospective.

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

Scrum Values make the use of Scrum successful. How can the Product Owner use these to grow trust within the team even more? Check it out!

Die gute Nachricht: Scrum ist ein Rahmenwerk, in dem sich Methoden wie Design Thinking und Lean Startup gut integrieren lassen. 

In Kürze: Die Scrum Master Zertifizierungen PSM I, PSM II und PSM III bestehen Im ersten Artikel dieser Miniserie wurde festgestellt, dass man kein Zertifikat braucht, um gut in dem zu werden, was man tut, zum Beispiel als Scrum Master zu arb

Dies Frage kommt hoch, wenn wir die Verantwortlichkeiten des Scrum Teams und der Developer:innen diskutieren.

The Scrum Guide defines Sprint Goal as the single objective for the Sprint, is a commitment by the Developers, and is part of the Sprint Backlog.

Scrum is simple, but that simplicity means that each of its elements is essential.  The values, accountabilities, artifacts and events are all part of the framework for a reason.  Teams that mess with the framework are messing with Scrum.  Teams that make changes to the elements limit Scrum's effectiveness and aren't really using Scrum.  This article discusses some of the things in the Scrum framework teams shouldn't mess with but often do. 

The first article of this mini-series established that you do not need a certificate to become good at what you do, for example, working as a Scrum Master.

Ich bringe Teams bei, wie sie UX-Praktiken und Scrum verbinden können.

Warum Sie keinen Nutzen aus Scrum ziehen können, wenn Sie nicht in jedem Sprint Done Increments erstellen – und wie Sie dieses Problem lösen!

Scrum Values make the use of Scrum successful. How can these values bring more Transparency to your Increment? Check it out!