Artificial Intelligence is transforming how teams do their work. AI assisted coding has taken teams by storm, every team now uses one or the coding agent like Claude or Copilot. All the work, all the changes are becoming faster, data-driven and augmented by AI. However, with all this technological advancement and if I may call it the rat-race of creating the next AI driven product, one question is getting overlooked: Is Psychological Safety still intact when AI enters the team?

Kate was a Business Analyst for 12 years in an IT company in Greece. Once she made a definite decision to jump out of her comfort zone and become a Scrum Master. Let's walk through her story.

The rise of AI-enabled Scrum Teams has fueled debate over Sprint Length, with some proposing daily Sprints due to AI's high productivity. However, shortening Sprints or broadening goals must prioritize human and organizational constraints over raw output. Key considerations include the limited Availability of stakeholders for frequent feedback and the risk of cognitive overload from reviewing massive amounts of AI-generated content. Teams should consider using the time saved by AI to improve the product's operating model, conduct research, or invest in training, rather than simply increasing the scope of the goal (Focus and Value). Furthermore, the rapid emergence of new AI tools makes historical data for Predictability less valuable, suggesting a focus on timeboxing the most valuable Sprint Goal. Ultimately, the ideal Sprint length must account for stakeholder capacity, feedback cycles, and the scope of the broader value stream, not just the speed of AI delivery.

After more than 20 years coaching Scrum Teams, I’ve learned the interview isn’t just about them judging me: I’m judging them right back. I’m looking for clues about whether this is a place where I can actually help teams improve, or if it's just not a good fit for me.

In this blog, David Spinks discusses the importance of true stakeholder collaboration, and why using tools like a stakeholder map may not be enough to achieve it.

En este artículo el PST Alex Ballarin explica como descomponer bien las épicas en historias de usuario. Además recuerda el origen y verdadera utilidad de este formato de paquete de trabajo, e incluye ejemplos prácticos de como escribir buenas épicas, features e historias de usuario.

Real questions hiring managers might actually ask

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

Scrum is no longer a specialist competency, but a fundamental literacy for anyone who wants to work in a collaborative, modern workplace. Let's review 8 powerful triggers that force people to learn Scrum.

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

A new edition of the FREE "Scrum Master Interview Questions Guide" is available: 97 Questions, including guidance on answers and red flags, covering all relevant fields.

When AI commoditizes execution, competitive advantage shifts to organizational context and learning speed, operating model capabilities most organizations have broken or never built.

En este artículo el PST Alex Ballarin reflexiona sobre qué debe saber el Scrum Master acerca de los aspectos éticos y legales de la IA. Estas responsabilidades suelen estar en los tejados de los departamentos legal y otros, pero los equipos también deben conocerlas y co-responsabilizarse de los efectos de su trabajo.

It is said that Developers are committed to the Sprint Goal and flexible about the scope of the Sprint. But what does it mean?!

Too many people throw around terms like 10x developer or 100x team. I want to talk with you about the -100x team.

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.

Many teams blame the Daily Scrum when it starts feeling repetitive, pointless, or performative. But the meeting is usually not the real issue. The real issue is weak transparency: the team cannot clearly see what is true, what threatens the Sprint Goal, and what should change today.

Most teams “do Scrum.” Few see real ROI. Here’s how Scrum drives growth by cutting costs, accelerating delivery, and aligning work with customer value, plus practical tactics you can apply immediately by PST Robb Pieper.

Seu produto está morrendo na lama operacional? Entenda por que POs e empreendedores falham ao ignorar a conexão entre o negócio e o backlog. Usando o exemplo prático de uma padaria artesanal, aprenda como transcrever o Business Model Canvas em uma estratégia de produto matadora e alcance o Product-Market Fit de uma vez por todas

In Scrum, there are three artifacts helping us keep transparency high. But what are their practical shapes?

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 ...

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

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.