Reflecting on 10 years at Scrum.org, in this post, Dave West explores the core of the agile movement: empowering people and teams. Contrary to popular agile sentiment, middle management is not the problem but the key to success, as they create the environment for change. The persistent challenge of achieving true empowerment requires understanding and shifting organizational power structures and incentives. Finally, Dave considers AI as a potential catalyst—a "missing piece"—that, when combined with frameworks like Scrum, could finally unlock the door to fully empowered teams.

The UK’s new SME Office signals progress, but real change needs adaptable delivery, smarter contracts and risk-based governance. SMEs bring speed and focus, yet face barriers baked into procurement and policy. Success will hinge on measurable shifts in participation, payment speed, modular contracting and genuine discovery-led delivery.

Self-management is crucial for any Scrum Team’s success, yet many teams and organizations struggle to truly embrace it. So what can you do about it? In this blog, PST Robb Pieper shares practical ways to enable and support real self-management.

The AI Fluency framework helps us build a mindset of how to think about working with AI. But how?!

A 40+ team retail division transformed delivery through a fundamental culture shift: from starting work to focusing on finishing it, creating trusted predictability.

Self-organization is not something that needs to be earned. And besides that - to be honest - deciding what teams' people will work on is not rocket science either. By trusting the team to own how they work together to deliver the product, the organization is empowering them to figure out the best way to deliver the product.

Okay, let’s talk numbers. Real ones. Actual data shows how Asia, and especially Singapore, is diving headfirst into Agile and Scrum at a remarkable pace. Adoption is rising, investment is soaring and the region is transforming faster than ever. But the real story is what these numbers reveal about the future of work in Singapore and why deep, real Agile understanding matters now more than ever.

In diesem Artikel beschreibt PST Simon Flossmann die Auswirkungen von „Wir machen Scrum, aber...“

La innovación y el aprendizaje son recursos claves para la ventaja competitiva de las organizaciones en los entornos de cambio. Pero lograr esto requiere de un ambiente donde los equipos tengan un ambiente de seguridad emocional apropiada. Tener equipos motivados, preparados, con hambre para lograr objetivos y mejorar es crítico para que aparezca la creatividad y la innovación de productos. Difícilmente las personas en forma individual pueden lograr los cambios necesarios para producir productos innovadores; es un trabajo de equipo con un liderazgo que promueva esta cultura y la sostenga a través de sus acciones y se comprometa con ese cambio. En esta entrega exploramos algunas consideraciones para los líderes sobre cómo lograr un ambiente creativo, con equipos motivados, autogestionados para aprender, mejorar y lograr los objetivos son las siguientes:

Most transformations fail not because organizations lack frameworks, but because they lack the measurement systems to prove value delivery and guide continuous improvement.

Compare your context with functional, product, customer, and multidimensional structures. Identify what fits your strategy — the right structure enables it, the wrong one slows it down.

What do to about the Sprint schedule during the holidays?

If your Sprint Review is starting to feel a little pointless, ask yourself: Do we have a clear direction? And are we collaborating together to adjust course and find the best path to get there?

In last week's Professional Agile Leadership class, I asked leaders to share what interview questions that they would use to find a great Scrum Master. With their permission, I’m sharing the questions that the group came up with.

Scrum Teams don’t need all skills from day one—they need the courage and discipline to practice. Skills are muscles, built by doing, reflecting, and improving together. The real question isn’t which skills you have today, but which skills you’ll practice tomorrow.

Most organizations confuse product thinking with structural or linguistic changes — renaming roles and reorganizing teams — without building the systemic capabilities that make it real. True product thinking requires developing discovery, decision-making, collaboration, and learning systems that enable continuous adaptation and value creation.

Dieser Artikel identifiziert die Erfolgsfaktoren für Agilität, die in Ihrem Unternehmen fehlen. Er bietet Ihnen konkrete Maßnahmen, die Sie am Montagmorgen umsetzen können, um zu prüfen, was Sie in Ihrem Einflussbereich an Veränderungen vorantreiben können.

When you’re kayaking in fast whitewater, the boat tends to go wherever you look. That's because when you look at something, your whole body tends to lean that way without you even realizing it.

Scrum balances three forces—strategy, tactics, and risk—through the Vision, Product Goal, and Sprint Goal. The Product Goal bridges the gap between long-term vision and short-term execution, ensuring focus, alignment, and manageable risk in complex environments.

The Truth Curve isn't a one-time linear process; it's an ongoing loop. The process of "earning" truth through small, repeatable cycles of learning is called Continuous Discovery.

En este artículo, el PST Alex Ballarín explica como alinear a los equipos Scrum con la ejecución estratégica y los OKR es una opción que potencia su efectividad, autonomía y resultados.

When Scrum Teams blend Kanban with Scrum, they benefit from more predictable delivery, early detection of spikes in demand, sustainable pace, and data-driven decisions.

What manufacturing taught us about knowledge work — and why Ackoff knew we were asking the wrong questions

In diesem Artikel beschreibt PST Simon Flossmann, wie Produktrisiken eliminieren werden können.

Experienced Scrum practitioners often reach a plateau where the mechanics are mastered, but the outcomes still feel constrained and inefficient. If you are comfortable with Scrum and ready to evolve your practice, consider an approach that reframes the Product Backlog and Sprint Planning around value and outcomes rather than stories and estimates.

This article identifies the success factors for agility that are absent in your organization. It gives you concrete Monday-morning actions to test what’s actually possible within your sphere of influence to drive change, because agility matters.

Many organizations misinterpret success as making the Scrum Master obsolete. It sounds efficient, but it removes the very accountability that sustains empiricism. The Scrum Master’s role doesn’t vanish when a team becomes self-managing. Their focus shifts from facilitation to coaching, from team habits to organizational change, from removing blockers to transforming systems. They serve the Scrum Team, the Product Owner, and the organization. When they evolve their focus, agility scales. When they disappear, complacency takes their place.

A guideline to help leaders grow trust and accountability

Kanban Boards make visible the flow of value – items of value. In a Scrum context, those items are Product Backlog Items. (Not the decomposed tasks of the Sprint Backlog.)

In Scrum, *collectively* doesn’t mean everyone must master every skill. It means the team as a whole has the skills to deliver value. Discover why this matters, how to avoid the “Lego block” myth, and how to grow resilience by sharing and acquiring skills.

In this article, PST Alex Ballarin explores how Objectives and Key Results (OKRs) complement the Agile Product Operating Model (APOM) from Scrum.org. He explains how OKRs bring measurable alignment to APOM’s four domains — Strategy, People, Structure, and Value Cycle — turning strategic intent into evidence-based results and enabling true organizational agility.

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.

Dieser Artikel und sein zugehöriges Video über die KI-Risiken in der Produktentwicklung zeigen drei konsolidierte Risikokategorien und praktische Grenzen auf, um ein kundenorientiertes Urteilsvermögen zu bewahren und gleichzeitig KI effektiv zu nutzen.

Where in Singapore can you learn Agile and Scrum the way they were truly intended? Where can you find training that goes beyond personal opinion and is grounded in global standards, local relevance, and the authority of the organisation that created Scrum? That is exactly what Kiwii Pte. Ltd. brings to Singapore. This blog is the first in a broader series in which Scrum.org trainer Chee-Hong Hsia shares his perspective on Agile in Singapore, exploring the realities, misconceptions, and opportunities within our local landscape.

In diesem Artikel erklärst PST Simon Flossmann ein Methode, die jedes Meeting verbessert.

When Your Leverage Becomes Your Liability Because You Outsource Thinking.

Competitive advantage comes from minimizing the time between decision and learning — the faster you validate assumptions with real user feedback, the faster you can adapt and create value. Traditional projects optimize for delivery and predictability, while product thinking optimizes for continuous learning, reducing risk, accelerating revenue, and turning responsiveness into a strategic edge.

Delivery isn’t the finish line — real success comes when a shipped feature creates measurable outcomes and impact. By extending “Done” beyond delivery to include learning and evidence of value, teams shift from output-focused activity to outcome-driven results that truly matter.

In fast-changing markets, traditional hierarchies still help leaders see the big picture, but they struggle to keep pace with reality. As information travels upward and decisions come back down, organizations risk losing focus on customers and slowing adaptation. Agile organizations take a different approach: they emphasize connectivity over control. Decisions move closer to the customer, supported by connected teams, shared data, and shorter feedback loops. Creating Agile Organizations (CAO) reframes the challenge: Shift from reporting to connecting across teams. Design for tight coupling inside product groups and loose coupling between them. Use AI to amplify local decision-making, not to recentralize control. The result — organizations that move fast locally while staying coherent globally.

Scrum isn’t powered by lone heroes—it thrives when groups of people engage together. From teams to stakeholders to leaders, Scrum creates the structure for collaboration, transparency, and shared purpose. Which groups are you engaging—or leaving behind?

Most organizations are attempting to build the future of AI on the crumbling foundation of a rigid, outdated, project-based funding system. This approach is fundamentally mismatched with the iterative, experimental nature of AI development. To truly unlock business value, a shift is required—from funding temporary projects to funding durable products.

La adopción de Scrum puede ser un proceso complejo, difícil y sin rumbo en muchas organizaciones. Algunas veces se inicia su adopción sin tener en cuenta los beneficios y el esfuerzo de cambio necesario para lograr los resultados de negocio que se esperan; en algunos casos, las organizaciones pueden hasta decidir cancelar sus proyectos de cambio por el desánimo de los resultados. Aquí algunos factores que pueden ser tomados en cuenta para mejorar el éxito de la adopción de Scrum.

Many teams adopt Scrum successfully but struggle to gain the support of their executives. In this blog, PST Robert Pieper shares how leaders can shift their perspective to see agility as a company-wide advantage that drives better decisions, stronger collaboration, and measurable business results.

The Psychological Safety Radar helps you build a space where people: Speak with honesty Listen with empathy Learn with humility Grow with courage

The most successful Scrum Teams adopt the product model by organizing their Scrum Teams around products. Because dependencies are the bane of value delivery!

In diesem Artikel stellt PST Simon Flossmann 3 Fragen vor, die sich Product Owner viel zu selten stellen.

Scrum Teams don’t exist in a vacuum. The Scrum team's success—or failure—is heavily influenced by the broader organization around them.

Tiny organizations crushing giants — without process, without friction.

Executives keep hearing that “95 percent of AI projects fail.” The truth is uglier: it’s not the models that are failing, it’s the management operating systems we’re using to leverage them.

When we were developing the Professional Scrum with Kanban guide and class, Daniel Vacanti kept insisting I inspired the Work Item Aging flow metric we introduced. I was complimented, but didn’t recall the exact reference. Well, it turns out I did write and talk about this way earlier than the PSK.