Most problems in Scrum don’t come from misunderstanding the framework. They come from applying reasonable thinking in the wrong context. These cognitive traps show up as decisions that feel right—more efficient, more controlled, more predictable—but quietly undermine transparency, inspection, and adaptation. This overview outlines ten of the most common traps and how they distort delivery in practice.

In this blog, I want to discuss a powerful phrase that has come up in my interviews and research: AI is the next printing press. The analogy is powerful because, just as the printing press turned knowledge from a scarce luxury into an abundant product, AI and automation are acting as a "cognitive printing press" by democratizing capabilities. This lowers the barriers for knowledge workers, even for someone like me who is not a front-end developer, to rapidly create and adapt products, greatly accelerating the delivery pipeline. While I am ultimately a techno-optimist, I recognize that the printing press analogy also offers a word of caution, highlighting potential risks such as quality issues (like "hallucinations"), job displacement, and the pressing need for new regulation and ethical frameworks. To navigate AI's impact, I believe agile product developers must focus on three critical things: improving and changing the innovation pipeline, ensuring governance is robust through transparency and separation of controls, and doubling down on discipline and professionalism.

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.

Many Scrum Masters think they should update the Sprint Backlog, but ...

Most mistakes in Scrum aren’t because people don’t understand the framework—they come from applying reasonable thinking in the wrong context. Cognitive traps happen when decisions favor efficiency, control, or comfort over transparency, inspection, and adaptation. Here is one of ten cognitive traps: efficiency over empiricism.

スクラムは、スクラムのフレームワークに従うことで効果を発揮できるようになっており、そこからチームと組織の自発性、自律性、複雑な問題へ取り組むことに対して主体的になれるような仕組みが備わっています。また、意図的に不完全にもしています。この利点を活かしたスクラムへの取り組み方を紹介します。

In this article PST Simon Flossmann shares 3 levers for better team performance.

In diesem Artikel beschreibt PST Simon Flossmann seine Erfahrung nach 10 Jahren IT-Beratung: Diese 5 „Feinde“ verbrennen das Budget – noch bevor Features live gehen

Many change efforts hit a wall - not because the idea is bad, but because organizations work like tensegrity structures: highly interconnected, under tension, systemic. Understand that, and you'll approach change differently. As a Scrum Master, this might be the missing piece you've been looking for.

AI's last mile isn't a technology gap. It is an operating model gap in which decision flows, knowledge capture, and governance design determine whether pilots deliver enterprise value.

Most micromanagement is not a control problem; it is a clarity failure in disguise. This article introduces Commander’s Intent: a five-part briefing model that replaces prescriptive instructions with shared purpose, hard constraints, and room to adapt.

Scrum é um quadro de trabalho de trabalho para lidar com problemas complexos em ambientes complexos. A unidade fundamental do Scrum é a equipa. Scrum é muito mais sobre comportamento e interacções do que ferramenta ou processo. Sem os Valores do Scrum: Compromisso, Foco, Abertura, Respeito e Coragem, o Scrum perde a sua essência e transforma-se num processo fixo com um conjunto de reuniões pré-agendadas com pouco ou sem impacto real. Equipas e organizações passam a privilegiar output em vez de aprendizagem e outcomes, escondem problemas, evitam decisões e conversações difíceis e pouco aprendem. Na era da Inteligência Artificial, este risco aumenta: a velocidade cresce, mas sem empirismo, também cresce o desperdício. Viver os Valores do Scrum não é opcional — é o que permite às equipas aprender, adaptar-se e criar valor de forma consistente num contexto de elevada incerteza.

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.

This article argues that what looks like “broken Scrum” is usually a fundamentals problem underneath — especially weak transparency, inspection, and adaptation. It helps readers spot that pattern fast, then gives them a practical counter-move they can apply instead of adding more process theatre.

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

Short piece on how to use organizational mapping to connect strategy, capabilities, and structure, check whether your organization design really supports its goals, and redesign it when it does not.

En este artículo el PST Alex Ballarin explica cómo la IA es una gran oportunidad para los product owners, y da ejemplos de 5 prompts de IA que

In this long tutorial, I explain how a great Scrum Master spends their time in a regular Sprint.

Some Scrum Teams use specific Sprints with specific names for specific purposes. But there is a problem with this approach.

If you have both business and technical people on the same Scrum Team, let me start with this: That’s awesome!

If your organization is learning how to run Scrum when half your team is AI agents, you already know that traditional Scrum events require a change. The Sprint Review is no exception. In a traditional setup, the human developer who built the feature takes pride in demonstrating it to the stakeholders. But who demos the product when an AI agent builds it?

An overview of Front–Middle–Back archetypes for multi‑dimensional organizations, with three structural patterns and real examples from Salesforce, AWS, USAA, Siemens, Philips, SEB and Samsung.

We are used to seeing visualizations for the first two artifacts, Product Backlog and Sprint Backlog. But, how about the third one, Increment?!

In diesem Artikel erklärt PST Simon Flossmann 5 Fallstricke, die Product-Owner-Karrieren sabotieren

How do you support your team? How do you bring out their creativity and wisdom, their curiosity and determination, and skill growth? The answer is servant leadership. In this post, we will explore 5 actions of an effective servant-leader.

En este artículo, el PST Alex Ballarín explica con cinco ejemplos de prompts para tu LLM favorito, como la IA puede potencial el trabajo del Scrum Master en las organizaciones.

Change fitness is a measurable organizational capacity that depletes under concurrent transformation load. Most organizations diagnose resistance when the real problem is depletion.

Multi-dimensional org design beats classic M-form: a front–middle–back model that unites products, customers and shared platforms into one system to unlock cross-segment value and scale.

Do you move undone PBIs directly to the next Sprint?! Then you need to watch this video.

Decisions run on perception, not truth. Here’s how to tighten it.

In diesem Artikel beschreibt Mark Rehberg warum für Teams die Art der Veränderung nicht so wichtig ist. Die Veränderung aber notwendig.

Dieser Artikel argumentiert, dass Jira kurz davor steht, von der Wissensautorität zur Ausführungsoberfläche degradiert zu werden — Kontext ist wichtiger denn je.

Muitos profissionais dominam o Scrum na execução, mas ainda têm dúvidas sobre o que realmente deve ser construído. Este artigo explora como o Product Discovery complementa o Scrum ao ajudar times a identificar problemas relevantes e reduzir incertezas antes de investir em delivery

Many Scrum Masters believe they should be present in the Daily Scrums, but ...

Como Scrum Master es ideal desarrollar la habilidad de escucha activa en el equipo. La escucha profunda, reflexiva y con empatía es diferente a escuchar para refutar y rechazar. Recibir, entender y agradecer todos los aportes puede ser el inicio de un conflicto constructivo, saludable y creativo para enriquecer las soluciones que se puedan lograr. En este post se aportan algunas ideas sobre como el Scrum Master facilita la solución de conflictos.

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.

“Wir machen ein Experiment, aber am Ende muss es funktionieren!” Diesen oder ähnliche Aussagen kennen wir zu genüge, wenn es darum geht, dass ein Team Dinge ausprobiert um das Teamspiel zu verbessern. In diesem Artikel beschreibt Mark Rehberg, woran man "echte" Team Experimente erkennt.

Your Sprint length depends on two main forces. Let's check them.

The integration of autonomous AI agents into software teams requires us to rethink how we approach our Scrum events. When half of your contributors are machines, the traditional Daily Scrum fundamentally changes.

How should we limit WIP on the Portfolio Kanban? How is a Portfolio-level kanban system different when it comes to limiting WIP? Shifting from capacity management to leadership focus management

En este artículo el PST Alex Ballarín nos explica porque la Definición de Hecho es todavía más importante en la época del desarrollo de software con IA, como puede adaptarse este artefacto para seguir siendo efectivo y además muestra un ejemplo ilustrativo de Definición de Hecho adaptada a IA.

En este artículo, el PST Alex Ballarín te explica como la IA generativa puede ser una gran compañera para preparar eventos de Scrum más valiosos y orientados a fomentar la colaboración entre los miembros del equipo. Además puede reducir significativamente el esfuerzo del Scrum Master a este efecto.

En este artículo el PST Alex Ballarín explica como los cambios de la IA en las organizaciones son sistémicos, y como el Scrum Master tiene experiencia en facilitar cambios complejo como este a través de la transparencia, inspección y adaptación.

This article argues that the tool on which 62% of agile teams rely is about to be demoted from knowledge authority to execution interface. We need to move from Jira to AI Agents.

Someone notices a problem. Should we knock it out now?

In this article, PST Simon Flossmann shares 3 insights about setting Sprint Goals.

In diesem Artikel erklärt PST Simon Flossmann warum 90 % der Product-Owner diese Sprint-Review-Änderung meiden

Organizations don't become complex by accident. Complexity is accumulated decision debt from thousands of reasonable local decisions that create an unreasonable system. Simplification requires the same rigor as creation.

Imagine someone asks you to explain what Agile is. What would you say?!

The work means the result: stop doing status, start showing reality