The Scrum framework offers clear rules, guidelines, and constraints. Teams can use these as boundaries to self-manage and self-organize their work, minimize risk, and deliver value to their stakeholders. When teams are relatively new to Scrum, strictly following the rules and constraints makes sense. But what if a team wants to change the rules of Scrum? In this blog post, I share my thoughts.

What we measure is what we get? If there is no focus on defining what we want to achieve and articulate how we can measure it then often we end measuring wrong stuff and that impacts our ability to create value, to be successful.

In diesem Artikel erklärt PST Simon Flossmann, die 3 Versprechen, die Agile Transformationen einlösen müssen.

This article outlines seven key development directions for Project Management Offices to effectively support modern product-oriented organizations. Transitioning from a project to a product-oriented operating model requires organisational change in culture, processes, and management. This will result in transforming current PMO services to become more Agile and product-oriented .

La servant leadership emerge come paradigma fondamentale nella risoluzione di sfide complesse. Lo Scrum Master, incarnando questo approccio, trasforma il modo tradizionale di guidare i team verso risultati sostenibili e significativi.

2024 ended with my vision becoming reality: A small group of people gathered in Costa Rica to experience a unique approach to leadership development - learning to ride the waves instead of trying to control the ocean - at the Agile Leadership Surf Camp. Learn 5 key insights that emerged from this experience.

In Scrum, the Definition of Done (DoD) is a shared understanding of what it means for a Product Backlog item to be considered complete. For example, for a Scrum team that is developing software, a Definition of Done might include things such as 'Complete code review' or 'all standard Regression scripts have passed' or even 'performance testing complete' or 'page loads in under .1 seconds'.

In this article, Natasha Hampshire and David Spinks discuss common perceptions of product development research and what it means for agility.

In his latest blog post, PST Mehdi Hoseini summary of the DORA report 2024 including the most important insights of the report especially the impact of AI on the software development field.

In this episode of the Take5IRL podcast, PST Jeff Lee is joined by Peter Borsella, co-founder of Big Orange Square, and a leading expert in Agile for hardware. Together, they uncover the fascinating story of a company struggling to keep up in a competitive market.

Personal retrospectives can help you improve your life. This approach, similar to team retrospectives, encourages self-reflection. By assessing different areas of your life and identifying areas for protection and improvement, you can focus on a few small, actionable steps to achieve your goals and improve your overall well-being.

In diesem Artikel stellt PST Simon Flossmann vor, wie du mit Liberating Structures das Sprint Planning gestallten kannst.

Start-up Agility describes the mental disposition within which leaders can learn to swim through uncertainty, build their teams in ebbs and flows, and deliver value at every growth point. By fostering connections, empowering teams, and remaining flexible, agile leaders set up the engagement for sustainable success. Let’s discuss how Agile leadership can revolutionise your Start-up. Leave a comment on your thoughts, or contact us for more stimulation!

Wenn Du in all dem noch neu bist, fragst Du Dich vielleicht: Worum geht es bei Agilität überhaupt? Wie können Organisationen oder Teams davon profitieren, agiler zu werden? ​

This is my work to welcome 2025—Scrum Tour: A quality informative gift to my audience. Enjoy the tour and I wish you all the best in the new year.

The term ‘backlog’ in Scrum refers to more than a list of features—it’s a tool for transparency, collaboration, and delivering value. Learn why shorter, focused backlogs empower teams and how expanding backlog items to include hypotheses, outcomes, and problems can drive innovation.

Adopt one of these New Year's resolutions at your next Sprint Retrospective!

Scrum es un marco de trabajo que ayuda a maximizar la entrega de valor a los clientes, mejorar los resultados de negocio y crear un ambiente cultural de trabajo en equipo basado en los valores de Scrum. A continuación, algunas recomendaciones para mejorar los beneficios de Scrum al entregar valor:

In diesem Artikel teilt PST Simon Flossmann, welche Artikel im Jahr 2024 am erfolgreichsten waren.

In this vlog, join hosts Andreanna Marshall and Grand Scrum Master Scott as they dive into practical strategies for implementing Scrum principles seemingly solo. 🚀 Discover how to navigate resistance and transform your workplace from the ground up!

Making the state of Agile transparent by shining light on problems, obstacles, and successes touches on the essence of what coaches and Scrum Masters should do. Yet many don't use a 'flashlight.' They wander through organizations in the dark, trying to figure out what’s happening. In this post, I explain why using a flashlight matters and how you can get started.

Instead of outcome, “We need to increase customer retention by 10%,” We ask: “What capability will keep improving customer retention over time?” Maybe it’s learning to gather and act on customer feedback faster. Maybe it’s the ability to run small, cheap experiments. Whatever your specific capability is, when you focus on building the capability, the outcomes take care of themselves. The real question is: What capabilities will make us better every day? Outcomes are the result—capabilities are the key.

In diesem Artikel teilt PST Simon Flossmann seine Erkenntnisse über Scrum über Produkt- und Organisationsentwicklung.

A common question for newcomers to Scrum: What Do You Think About Story Points?

In this episode of the Take5IRL podcast, PST Jeff Lee is joined by Peter Borsella, co-founder of Big Orange Square with Hubert Smits and a leading expert in Agile for hardware. Together, they dive into the unique challenges of applying Agile in hardware development—a world where traditional software practices don’t always translate smoothly.

Ordering the Product Backlog in Scrum isn’t just about deciding what’s important—it’s about creating a clear sequence of work for maximum value. Discover the key differences between ordering and prioritizing, and the criteria Product Owners use to arrange backlog items effectively

In diesem Artikel resümiert PST Simon Flossmann über das Jahr 2024 und teilt seine Erkenntnisse und Lektionen.

In this article, we will discuss 3 concepts that work better in simple business problems and not so well in an Agile environment.

In diesem Artikel erklärt PST Simon Flossmann, wie du als Scrum Master mit Bürokraten um gehst

Create a shared understanding of the benefits of Agile for your organization and make gaining them a shared responsibility. In addition, it creates a climate of continuous improvement in which progress is measured. How else would you know you're gaining the benefits of Agile?

Is your Portfolio Kanban Board Busy? Too many cross-product initiatives? Instead of investing in Portfolio management - Descale by Organizing around Outcomes.

La validation de la valeur d'un produit va bien au-delà de l'implémentation de fonctionnalités. Combien de fois vous est-il arrivé de publier une nouvelle fonctionnalité, convaincu que c'était exactement ce que vos utilisateurs voulaient, pour découvrir ensuite que personne ne l'utilise ? Dans cet article, nous explorerons cinq approches concrètes pour vous assurer que votre produit crée réellement de la valeur.

The Scrum Guide says a Product Owner ‘orders the work’ into a Product Backlog. But what does ordering really mean in Scrum? It’s not about commands—it’s about creating clarity and alignment. Explore the collaborative nature of ordering and its impact on the Scrum Team.

Negativity doesn’t just dampen morale -it can derail team performance entirely. This blog dives into the Bad Apple Effect, showing how just one negative individual can impact collaboration, productivity, and development in sports, business, and Agile teams. Ready to address negativity and build high-performing, adaptable teams? Explore how to tackle toxic behaviours and foster a culture of continuous improvement. Dive in to learn more!

E.L.E.V.A.T.E. A Transformative Model for Product Owners to Invest in Themselves

So you have a Portfolio Kanban board managing your biggest investments. You’re actively managing the flow by using this Kanban board in your conversations about the portfolio. Kanban/Flow Metrics can help sharpen your flow focus even further. The four flow metrics described in the Kanban Guide for Scrum Teams / Kanban Guide are Work in Process (WIP), Cycle Time, Throughput, Work Item Age (WIA). How can these metrics help us at the Portfolio level?

In diesem Artikel erklärt PST Simon Flossmann, wie Scrum Master ihre Wirkung potenzieren können.

In diesem Artikel werden wir die Bedingungen untersucht, unter denen reines Scrum gedeiht, die organisatorische DNA, die zu seiner Unterstützung erforderlich ist, und praktische Szenarien, in denen es am besten funktioniert – zusammen mit einem ehrlichen Blick darauf, wo es Schwierigkeiten bereitet.

They tell us a story of slow, centralized decision-making, often related to classic program management culture combined with an iron spaghetti portfolio where delivering product outcomes often requires wide collaboration across teams and even teams of teams.

Product definition is a complex, political and challenging task in large IT organizations. In this blog we discuss what organizations need to consider when looking at their product model. We discuss why shared services could be candidates to become products and the value of tying product to strategy and value. We provide some simple questions to ask of your products to help guide the selection and remind the reader that product models like organizational structures require people and people come with politics.

Elevating Katas: Driving Continuous Improvement in Organizational Topologies In the evolving landscape of software development and organizational design, Elevating Katas play a crucial role in fostering continuous improvement. These structured, repeatable exercises help teams refine their workflows, challenge inefficiencies, and push for higher performance.

La validazione del prodotto è fondamentale nel mondo dello sviluppo prodotto moderno. In questo episodio, Fabio Panzavolta esplora cinque casi emblematici di prodotti che, nonostante gli ingenti investimenti, hanno fallito sul mercato per mancanza di una corretta product validation. Attraverso questi esempi, scopriremo come un approccio sistematico alla verifica delle ipotesi di prodotto e al product discovery possa prevenire costosi insuccessi.

A common mistake Product Owners (POs) often make is assigning Product Backlog items to specific Scrum Teams or individuals. While this approach may seem efficient - and even helpful - it undermines team dynamics, disempowers Developers, and distracts the PO from their true purpose: maximizing value.

Agile promises efficiency, but why do we keep adding people? An executive once asked me:
"We’ve been practicing Agile for years. It’s supposed to bring improvements, right? But we keep adding people. Where are the freed-up resources?" This question really made me pause and think. Agile is designed to help organizations deliver more value, not necessarily reduce headcount. But if the efficiency gains from Agile aren’t explicitly aligned with strategic goals, they often get absorbed into “doing more stuff.” The result? More features, more people, more meetings—but not always more value.

This article explores the conditions under which pure Scrum thrives, the organizational DNA required to support it, and practical scenarios where it works best—along with a candid look at where it struggles.

In diesem Artikel räumt PST Simon Flossmann mit 7 Mythen zum Sprint-Backlog auf.

In questo episodio, Fabio Panzavolta esplora la differenza tra output, outcomes e impatto in Scrum, elementi fondamentali per comprendere il valore generato dal lavoro del team. Scopriremo come questi tre livelli di risultati si collegano tra loro e quale ruolo gioca il Product Owner nel massimizzare il valore per l'organizzazione.

In questo episodio Fabio Panzavolta esplora come lo Scrum Master agisce da vero agente del cambiamento organizzativo, guidando team e azienda verso una maggiore agilità. Scopriremo le strategie pratiche e gli approcci concreti che uno Scrum Master utilizza per promuovere il cambiamento e migliorare l'efficacia dell'organizzazione.

Two fundamental approaches to managing work in organizations - the flow perspective focused on efficiently processing work units through defined stages, and the product perspective centered on continuously evolving product value for customers - shape how organizations structure themselves and measure success. This comparative analysis examines how these contrasting viewpoints influence organizational structures, management practices, and performance metrics, with particular relevance for organizations transitioning to product-oriented operating models. Understanding these perspectives is crucial for leaders making strategic decisions about how to organize and manage work in today's digital economy.

The Scrum Guide emphasizes the importance of fostering an environment for success—not controlling teams or stakeholders. Discover how Scrum Masters can shape the conditions for growth, collaboration, and effectiveness at every level.