Most Sprint Retrospectives do not fail because people did not talk. They fail because the team avoided the real issue and left without changing a damn thing in the next Sprint.

The landscape of software development has permanently changed. You should also adapt to the AI era and refine your events to induct AI agents in your Scrum Team

In diesem Artikel teilt PST Simon Flossmann 3 KI-Prompts mit denen typische Probleme in Scrum Teams im Handumdrehen lösen lassen.

En este post el PST Alex Ballarín explica como potenciar la efectividad de las retrospectivas de Scrum usando la IA: variar los formatos, preparar mejores preguntas, detectar lo que el equipo no dice, crear compromisos concretos y factibles y mejorar la propia retro.

It is always a question of how to manage the agreed improvements after Sprint Retrospectives, where you don’t want to miss any improvement items.

Are you prepared for the remaining days of a canceled Sprint? Let's check it.

Learn how Scrum reduces risk with 5 practical ways teams catch issues early, adapt quickly, and avoid costly mistakes in complex projects, in this post by PST Robb Pieper.

In diesem Artikel teilt PST Simon Flossmann seine 3 Lieblingsretrospektiven, wenn Teams nur schweigend in die Kamera starren

A practical way to leverage AI to increase the Sprint Retrospective effectiveness.

Psychological safety is foundational to Empiricism (Transparency, Inspection, Adaptation). If people are afraid to admit mistakes (like breaking the build), Empiricism dies. You can't have Empiricism without Safety.

Scrum events don’t work because they’re scheduled. They work because they create transparency, inspection, and adaptation. If nothing changes after your Sprint Review, Daily Scrum, or Retrospective, Scrum isn’t broken — it’s being ignored.

New Years is a time to pause and reflect - and that applies to Scrum Teams as well. So why not plan a New Years-themed Retrospective this year?

Scrum talks about *adaptation*—but not the kind driven by opinions, pressure, or discomfort. True adaptation only happens after transparency and inspection. Without learning first, teams don’t adapt—they drift. This post challenges how Scrum Teams really use adaptation.

The Scrum Guide uses “event” 24 times and “meeting” only twice. That’s not random. Scrum events aren’t meant for talking—they’re meant for changing. Learn how to make every Scrum event count.

Your stakeholders aren’t the enemy. They’re allies you haven’t asked yet. The Meta-Retrospective brings them into the room to work through what’s broken and what’s working; no agile jargon but real actions, and stakeholder buy-in for what needs leadership support.

Your Agile events aren’t failing because people lack training. They’re failing because your organization adopted the rituals while rejecting the transparency, trust, and adaptation that make them work. And often, the dysfunction of mechanical ceremonies isn’t a bug. It’s a feature.

Scrum events serve a purpose, but are they all necessary for every team? In this post, PST Jason Malmstadt discusses why each Scrum event exists and whether all of them are truly needed.

In diesem Artikel beantwortet PST Simon Flossmann die Frage: Welches ist das Wichtigste Scrum Event?

The Scrum Guide urges teams to base decisions on what is observed. But what does that look like in real teams, with real complexity? Let’s unpack the word and its impact.

Wir haben das alle schon erlebt: Sie bereiten sich auf die nächste Retrospektive vor und bitten ChatGPT um Hilfe: „Ich brauche ein paar Vorschläge für die Retrospektive“, tippen Sie. Was bekommen Sie zurück? Allgemeine Retrospektivenmuster, die Sie schon hundertmal gesehen haben.

What a shame: We are often ignoring the benefits of Meta Prompting, or having a conversation with the AI, before proceeding to the task.

If you’ve ever been a Developer on a Scrum Team, you’ve probably experienced this moment: you’ve completed all of the work you originally planned for the Sprint, and there are still a few days left. What now? It might seem like a good idea to just pull more work into the Sprint, but that sometimes c...

Scrum makes the impact of your practices visible—whether you like what you see or not. Learn what that means, and how to use it to improve your team's outcomes.

When a new Scrum Team first starts working together, they go through some common growing pains. Knowing what to expect for a new Scrum Team can help make things go a little smoother.

In diesem Aritkel beschreibt PST Simon Flossmann die Psychologie guter Entscheidungen.

Scrum Bingo is a fun way to reflect and sometimes laugh at our routines. But it also reminds us to be intentional with our words, honest with our blockers, and respectful of the team's time.

New Scrum Teams aren't perfect, but when you use Scrum to get better, you get better at Scrum. So often, when you first start using Scrum, it can feel like you're just going through the motions. And while that can be frustrating, it's also a part of learning.

In diesem Artikel warnt PST Simon Flossmann vor 5 Antipatterns, die erfolgreiche Retrospektiven verhindern

In this experiment, OpenAI’s new stealthy LLM Optimus Alpha demonstrated exceptional performance in team data analysis. It quickly identified key patterns in complex agile metrics and synthesized insights about technical debt, value creation, and team dynamics.

The 15-Minute AI-Enabled Prep for Scrum Masters and Agile Coaches to Build Trust

How "Strategy Knotworking" turns ideas and ambitions into reality, and why it's an excellent structure for your Sprint Retrospective.

In diesem Aritkel teilt PST Simon Flossmann seine 3 liebsten Formate für persönliche Retrospektiven

This blog post describes a 1-hour Retrospective format to help teams reflect on the empirical pillars of Scrum.

In some of my classes, people tell me they are using Scrum—but they can't call it Scrum. Why? Because someone in their organization had a bad experience with it.

In diesem Artikel teilt PST Simon Flossmann, 7 Tipps, wie du die Sprint-Retrospektiven moderierst. 

In diesem Artikel erklärt PST Simon Flossmann seine 5 Lieblings-Retrospektiven.

Scrum has been around for almost 30 years now yet there are so many misconceptions about what needs to be done and how it can be done effectively. Even today, as I coach and consult many teams I often see that the purpose of events is mostly lost. And people simply go through the motions, probably t...

In diesem Artikel gibt PST Simon Flossmann 3 Tipps, wie du Vielredner in Meetings unterbrechen kannst

In diesem Artikel erklärt PST Simon Flossmann, wie du Ecocycle Planning nutzen kannst, um die Working-Agreements zu verbessern.

In diesem Artikel stelle ich fünf umsetzbare Praktiken vor, wie Sie mit Retrospektiven zu echten Veränderungen gelangen.

In diesem Artikel gibt die PST Simon Flossmann 5 Tipps, wie du dich auf deine nächste Sprint-Retrospektive vorbereitest.

How to Make Retrospectives Lead to Real Change and Stop Spinning Wheels.

An effective Sprint Retrospective ensures the team remains cohesive and aligned, leading to sustainable development and innovation. It is a dedicated time for reflection, learning, and improvement.

In diesem Artikel teilt PST Simon Flossmann mit dir 5 Fehler, durch die Scrum Master die Sprint-Retrospektive unnötig verkomplizieren

In complex product development, consistency is crucial to achieving great results with Scrum. In this Responsive Advisors Lightning Round, PST's Robb Pieper, Greg Crown, Jason Malmstadt cover their top 10 best practices every Scrum team should follow to maximize value and ensure successful outcomes.

In diesem Artikel zeigt dir PST Simon Flossmann, wie du eine Sprint Retrospektive in 6 Schritten durchführen kannst, die langfristig den Teamzusammenhalt stärkt.

In diesem Artikel erklärt PST Simon Flossmann, was du tun kannst, wenn du in der Sprint Retrospektive in Zeitproblem kommst.

Eine Meta-Retrospektive ist eine ausgezeichnete Übung, um die Zusammenarbeit innerhalb des erweiterten Teams zu fördern, ein gemeinsames Verständnis des Big Pictures zu schaffen und wertvolle Handlungselemente zu erarbeiten

The Meta-Retrospective is an excellent exercise for fostering collaboration within the extended team, creating a shared understanding of the big picture, and immediately creating valuable action items.

I really can’t let this incremental delivery topic go. According to the 2020 Scrum Guide, “Scrum employs an iterative, incremental approach to optimize predictability and to control risk.” This means that Scrum Teams deliver a done, usable increment of working product frequently. This approach ha...