Scrum hat sich immer wieder als das beliebteste Framework für die Software-Entwicklung erwiesen. Angesichts der Tatsache, dass „software is eating the world“, ist ein erfahrener Scrum Master (m/w/d) heutzutage sehr gefragt. Diese Nachfrage führt dazu, dass Fachleute aus anderen Bereichen des Projektmanagements auf den Arbeitsmarkt für Scrum Master drängen, ggf.

There is often confusion in what happens in a Sprint with regards to the Increment and releasing. Short summary of this article: during a Sprint, one or more increments are produced. This happens when a Product Backlog Item meets the definition of "Done". At least once every Sprint, but it can happen more often. When a Product Backlog Item meets the definition of "Done" (and therefor becomes an increment), it can be released. Releasing can be done at any moment in time! 

In this blog, Mark Kachanov shares a step-by-step guide to introducing WIP limits to a team based on a real-life example.

Was können Nexus, LeSS, SAFe, Scrum@Scale und das Spotify-Modell?

The Canvas plays the role of a guide for the Team Coaches. The coaches can follow the guidelines of the Canvas and partner with their teams and their stakeholders to maximise the required abilities to move forward successfully, achieving the shared goals.

Scrum has proven time and again to be the most popular framework for software development. Given that software is eating the world, a seasoned Scrum Master is nowadays in high demand. And that demand causes the market entry of new professionals from other project management branches, probably believing that reading one or two Scrum books will be sufficient. Which makes any Scrum Master interview a challenging task. A good starting point, though, is to ask a candidate to walk in the shoes of an imaginary opponent trying to make the Scrum Master fail by culturally accepted means.

Personnellement j'ai toujours aimé travailler avec des équipes d'une dizaines de personne au maximum, avec un parcours qui leur permet de comprendre Scrum et l'utiliser à son plein potentiel. Il faut du temps pour y arriver et quand on y arrive c'est un vrai plaisir de voir un groupe de personnes devenir une Scrum Team !

Es gibt zwei Arten von Product Ownern...

In this blog, I will share my valuable experience in my journey toward becoming a Scrum Master. I would also share stories of various professionals, including women, who successfully got a Scrum Master’s job even after a career break. 

Esta semana, un alumni611 (un alumno de uno de mis cursos) me contacto con una duda sobre cómo tener agilidad escalada.

In this Blog, Dave West explores how we are transitioning into the deployment phase of the digital age.

Scrum ist ein einfaches, aber hinreichendes Framework für die Entwicklung neuer Produkte, vorausgesetzt, man identifiziert im Voraus, was es sich lohnt zu bauen. Aber auch nach einer erfolgreichen Discovery-Phase kann es einem Scrum Team schwer fallen, das Richtige zu erreichen, wenn das Product Backlog nicht den Anforderungen entspricht: “Garbage in, Garbage out” — wie man so schön sagt. Der folgende Artikel zeigt 28 Product Backlog Anti-Patterns — einschließlich des Product Backlog Verfeinerungsprozesses — auf, die den Erfolg Ihres Scrum Teams limitieren.

Scrum.org PST Chee-Hong Hsia is here to set the record straight. It’s actually a huge compliment when people say "You’re a Scrum purist".

In this blog, Venkatesh Rajamani shares tips on being a good Scrum Master.

Many well-meaning Scrum practitioners have misconceptions about Scrum, which sometimes leads to creating “rules” that do not exist in the framework. In today's article, we will discuss the five of the most common misconceptions about the Sprint.

So there is Scrum and there is 'an implementation of Scrum'. Why is it important to understand the difference? I hope that after reading this blog, you will realise that many Scrum conversations are actually not about Scrum, but "an implementation of Scrum" and you didn't even realise it.

Spark small and incremental change in your Scrum team, with our community-driven actionable quick tips.

Peut-on parler de management en Scrum?

TL; DR: Scrum 2022 — Getting You Started as Scrum Master or Product Owner Probably, you are considering how to further your Scrum Master career or Product Owner career in 2022.

2015 habe ich das Buch Lean UX gelesen. Überzeugt davon, dass Entdeckungsarbeit das Fundament der Produktentwicklung darstellt, fing ich an, die UX-Praktiken, die Jeff und Josh in ihrem Buch vorstellen, bei meiner Arbeit als Product Owner einzusetzen. Im Jahr 2018 besuchte ich das Professional Scrum mit UX-Training, um meine Erfahrungen, wie Scrum Teams erfolgreich User Experience in ihre Arbeit integrieren können, auf fundierte Beine zu stellen.

This is the third and final video in the series about responsibility. Here, Professional Scrum Trainer Mark Wavle talks through the powerful model, Circles and Soup.

Wie ein marktführendes Unternehmen ein internationales Projekt mit Scrum und dem Nexus Framework zur Skalierung agiler Teams zum Erfolg führte

5 Tipps, die Sie beim Skalieren agiler Teams beachten sollten!

Da ich bereits „Scrum Master“ bin, dachte ich, ich wäre bereits ein guter Facilitator.

Have you heard the quote by Deming “Without data, you’re just another person with an opinion”?

La productividad en Scrum. Scrum es un marco orientado a maximizar la entrega de valor usando el empirismo y el trabajo en equipo. En ese sentido la productividad se mide en base al valor entregado.

Es ist der Job der Scrum Master:in das Scrum Rahmenwerk zum Leben zu bringen. Und dennoch ist das keine Garantie, daß das Produkt erfolgreich wird. Es ist die Aufgabe der Product Owner:in den Wert des Produkts zu maximieren. Es werden 5 wichtige Elemente vorgestellt um Scrum gewinnbringend einzusetzen.

Automation is a vital practice for Scrum Teams. The best Scrum Teams I have been part of automated early and often.

Surprising insights from scientific studies into when and why code smells are introduced, and practical recommendations for how to write better code

Was ist Product Backlog Refinement? Scrum Teams machen es ständig. Es passiert im Sprint Review, nach dem Daily Scrum, im Sprint Planning und als Teil der Entwicklung. Sie diskutieren über die bevorstehende Arbeit, um sie zu präzisieren.

Eine lineare, schrittweise Abfolge von Änderungen — in der Regel durchgeführt von funktional getrennten Abteilungen — ist völlig unvereinbar mit der Änderungsgeschwindigkeit und Komplexität moderner Softwareprodukte.

In this second video in the series about responsibility, Professional Scrum Trainer Mark Wavle explores the leader's role in unwrecking responsibility issues.

A few years ago, before the pandemic, I visited an Agile conference in Kyiv, Ukraine. At the very end of it there was a panel discussion with some of the big names in the European Agile world.

In jedem Professional Scrum Product Owner Training werden die gleichen 10 Fragen gestellt. Und das zu Recht! Das sind die Dinge, mit denen die Teilnehmer am meisten zu kämpfen haben.

Here's my twist on an old classic. If I've learnt anything by writing this, it's that I should stick to training Scrum and not writing poetry!

SAFe® has always been a controversial topic within the agile community. Therefore, back in 2017, I ran a survey on the Net Promoter Score® of the Scaled Agile Framework SAFe®. The result back then was -52. Four and a half years later, I believe it is time to rerun the poll: SAFe® has been through several iterations, and many more agile practitioners have experienced working with it. Moreover, the question still is: Would you recommend SAFe ®?

Familiarize yourself with the principles of Liberating Structures and learn how they can strengthen your Scrum Team.

Extremes of responsibility are wreckers of teams and leaders. In this Unstuck Leadership Moment, Mark explores two unhelpful and unhealthy responsibility stances.

Wie können Scrum Teams in ihrer Entwicklungsarbeit den Nutzer niemals aus dem Auge verlieren? Hier 3 einfache Praktiken, die sie von YouTube, LinkedIn, Microsoft lernen können.

A common question we get asked is how do we get started with creating a Definition of Done? Let's explore how we can obtain transparency of where you are, your destination should be, and what your possible first steps are to get there!

La autoorganización es un proceso en el que alguna forma de coordinación surge de las interacciones entre los componentes de un sistema inicialmente desordenado.

A roadmap is a complementary practice that a Scrum Team might use to forecast upcoming deliveries or to translate Product Backlog items into a visual representation. This article includes a few Roadmap templates for Product Owners to use to communicate their forecast to customers and stakeholders. Give them a try and let me know what you think in the comments section!

If you are an agile leader - do you know whether your teams are currently operating at a sustainable pace? Do you care? Would you rather not know because you’re afraid of the answer? 

El Scrum Master es un líder servicial que se enfoca en el crecimiento de las personas, trabajo en equipo, la adopción del empirismo y la autogestión para ayudar a maximizar la entrega de valor. Ser exitoso como líder servicial se evidencia cuando las personas a las cuales se sirven son exitosas.

In this blog post, PST David Sabine shares a real life story focused around transparency.

Read on and learn more on how to best sabotage a Scrum Master from the exercise results of more than ten PSM I and PSM II classes. (I slightly edited the suggestions for better readability.)

Über 100 Jahre Industriezeitalter haben uns gelehrt, dass die Lieferung von Produkten den Erfolg eines Unternehmens bestimmt.

Myth 1 – Scrum is a Methodology To bust this first myth, I would prefer to differentiate between the concepts of methodology and framework. Methodology vs. Framework

In this Unstuck Leadership Moment, PST Mark Wavle explores the power of building a sense of ownership with the people we lead.

Last week, we talked about common misconceptions related to the Daily Scrum.  This week we’ll focus more broadly on misconceptions impacting everything from the Product Backlog to the composition of the Scrum Team itself.