As Artificial Intelligence reshapes the many industries and markets, many teams find themselves lost in a "fog" of hyper, uncertainty and cognitive overload. The "AI Sense Making" workshop offers a solution to navigate this complexity, drawing on established principles of sense-making to clarify direction. This workshop helps teams collectively discuss what might happen next. Based on that, they take actions to maximize chances of adapting successfully and reduces risk. This blog post outlines how to navigate the disruption caused by AI, and proposes a concrete way to facilitate team discussions and decision-making.

There’s an old expression, don’t gild the lily. It means to try not to over decorate something that’s already beautiful on its own. Sometimes I want to tell a Product Owner that I am working with not to gild the lily by overloading their requirements with solutions.

Scrum has helped teams embrace transparency, empiricism, and value delivery—but the same principles are urgently needed at the organizational level. As Ken Schwaber and Dave West remind us, honesty is a demanding yet essential capability, especially when applied to how we design and evolve our organizations. Our upcoming business novel, 10X ORG, explores this idea through the story of a leadership team uncovering the structural roots of their challenges—with a free preview available now.

Advanced Heat Map for Daily Banking: combining frequency and TCE‑based specificity to design economic boundaries of a product group, decide what to include, centralize or reconsider, and reduce coordination costs.

In diesem Artikel gibt PST Simon Flossmann Tipps, wie Scrum Master die PSM-III-Prüfung auf Anhieb schaffen können.

92% of organizations are increasing AI investment, yet only 1% achieve operational integration - not because of technology, but because they're running AI on industrial-age operating systems designed for stability, not evolution.

Eine User Story ist kein Mini-Pflichtenheft, sondern der Startpunkt für echte Zusammenarbeit. Ihr Wert entsteht nicht durch viele Worte, sondern durch Gespräche, Fragen und gemeinsames Verständnis. Warum weniger Schreiben oft zu besseren Ergebnissen führt, zeigt dieser Artikel.

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.

A Definition of Done should protect the business, not just signal activity. In this blog, PST Robb Pieper explains how a product-level Definition of Done reduces risk, supports real integration, and builds trust in what teams call done.

Business Agility isn’t about speed. It’s about focus and alignment. And it’s what helps teams and organizations maximize ROI, reduce risk, and adapt effectively to change. In this article, we explore what keeps organizations stuck, the building blocks of business agility, and how to get there.

A step-by-step guide for Product Owners on using AI to precisely transfer feature specs to Developers.

In diesem Blog Post beschreibt Mark Rehberg die Missverständnisse die Scrum häufig verursacht. Viele Organisationen führen Scrum mit der Erwartung ein, dass damit automatisch Probleme verschwinden: ineffiziente Prozesse, schlechte Kommunikation, unklare Anforderungen oder unzufriedene Kunden. Wenn sich diese Hoffnungen nicht erfüllen, heißt es schnell: „Scrum funktioniert bei uns nicht.“ Über diesen "Denkfehler" geht es in diesem Artikel. Scrum ist kein Problemlöser. Scrum ist ein Problemanzeiger.

Government delivery keeps repeating the same mistakes because legacy decisions, compliance culture, and risk-averse governance trap teams in outdated cycles. These ghosts of past, present, and future drain value and slow change. Real progress needs adaptive funding, flexible commercial models, stable teams, and learning that actually sticks.

AI is repeating the same mistakes we saw in failed Agile transformations: hype-driven adoption, weak leadership ownership, and poor alignment. This time, the impact is bigger. The AI Strategy Canvas helps leaders take a mindful, problem-first approach and build AI strategies that create real, sustainable value.

One of the most powerful tools Agile leaders have is also one of the simplest: asking great questions. Great questions don’t tell people what to do. They spark thinking. They nudge teams toward self-management. They build confidence and create space for creativity and innovation.

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.

In diesem Artikel erklärt PST Simon Flossmann die am häufigsten übersehene Aufgabe eines Product-Owners

Government tracks delivery, not value, mistaking activity for impact. Evidence-Based Management provides the missing discipline by measuring outcomes, learning, and real behavioural change. By shifting from status reporting to evidence loops, departments can link strategy to delivery, validate assumptions, and finally prove whether public investment is making a difference.

Most organizations measure AI adoption, not synchronization - focusing on usage instead of how well AI speed, Agile speed, and organizational speed align to create real business value.

Most organisations do not fail at agility because of their teams. They fail because their operating model quietly pulls them back to the Industrial assumptions they are trying to escape. The structures, metrics and leadership habits designed for stable, predictable work remain in place, no matter how much Agile language is adopted. Without disciplined operating-model hygiene, the organisation regresses, often without noticing, and agility becomes theatre rather than capability. This article examines why that hygiene is so hard, what it demands of leaders and how Scrum helps expose the work that must be done.

Portfolio management makes sure that money and people actually follow strategy, not just PowerPoint slides. When strategy and spending are misaligned, too many initiatives run in parallel, good ideas wait for funding, bad ideas keep going, and coordination overload quietly increases cost, risk and complexity. In CAO, the organisation is structured into product groups (with value areas), commodity platforms, and go-to-market units. Portfolio management decides how investment flows across these three: which product groups and value areas to grow or shrink, and which platforms to build, extend or retire—managed via a global portfolio, product group portfolios and platform portfolios. The model shifts focus from approving small projects to making a few clear strategic bets. With clear KPIs, loosely coupled product groups and shared platforms, leaders get sharper accountability, faster change, and better control of cost and complexity—especially when global portfolios are framed as product–market plays that align product, platform capacity and commercial focus around the same bets.

A Agilidade não morreu - mas sua aplicação superficial mostrou limites claros. Neste artigo, exploro como os Product Operating Models surgem para conectar estratégia, cultura, estrutura e operação, e como o Agile Product Operating Model(APOM), da Scrum.org, oferece uma arquitetura prática para escalar agilidade com evidencias, valor e contexto.

Scrum’s events are called formal for a reason. It’s not about rigidity—it’s about visibility and shared responsibility. Formal events ensure everyone inspects, adapts, and learns together. Skip them, and you lose transparency, alignment, and trust.

Government has frameworks and governance, but lacks the essential capability that ties strategy to delivery: product leadership. Without clear ownership, outcome focus, or strategic authority, teams default to reactive project behaviour. Professionalising product leadership would create coherent direction, evidence-based decisions, and stable teams able to deliver meaningful, user-centred outcomes.

This blog post addresses the confusion around the Product Owner accountability in Scrum. It clarifies that a Product Owner is a set of accountabilities, not just a job title, and that their core purpose is to maximize the value of the product delivered by the Scrum Team. Ultimately, Product Ownership is a significant opportunity to shape value and provide clarity, focus, and understanding, even in complex product environments.

Many leaders assume that psychological safety only thrives in democratic workplaces where challenging a manager is socially acceptable. But research shows something far more interesting. Psychological safety is not a democratic phenomenon. It is a human one. People everywhere want to prevent mistakes, ask for help, and contribute ideas. The difference lies not in the need, but the way that safety is expressed.

Agile helps teams deliver value sooner, reduce risk faster, and increase transparency while maintaining the ability to change direction quickly based on feedback and lessons learned. But one of the most powerful — and least discussed — benefits of Agile is that it exposes the problems that have been holding us back all along.

In this blog post, I summarized the DORA Report 2025. This year, their main focus was on AI. See the takeaways of the repost.

In diesem Artikel beschreibt PST Simon Flossmann, was er lieber früher über Scrum Masterei gewusst hätte.

What Agile practitioners knew about AI adoption - and why traditional change management was solving yesterday's problem

If your organization is putting in the effort but still feels misaligned, overwhelmed, or stuck in old patterns, the problem isn’t your process. It’s a missing set of core competencies. This article explores the three interconnected capabilities that help leaders and teams move from chaos to clarity. Together, they create the conditions for better decisions, stronger collaboration, and real adaptive capacity.

A breath of fresh air! I recently attended a meetup in Calgary and was happily surprised to hear a presentation about cutting-edge software development.

Most organisations are still run as if the world were predictable, even while their markets move faster than their governance, funding, and delivery can cope. This article contrasts the Industrial Operating Model with an Agile Product Operating Model, and shows how Scrum, Kanban, and Evidence-Based Management give leaders the enabling constraints to redesign their system of work for learning, flow, and genuine product outcomes rather than managed activity.

Skipping events? Trimming “non-essential” parts of Scrum? You’re not optimizing—you’re weakening the framework. Learn why Scrum’s value emerges only when its events and accountabilities are combined into one rhythm.

Ihre agilen Events scheitern nicht, weil den Menschen die erforderliche Ausbildung fehlt. Sie scheitern, weil Ihr Unternehmen die Rituale übernommen hat, aber gleichzeitig die Transparenz, das Vertrauen und die Anpassungsfähigkeit ignoriert hat, die für deren Erfolg unerlässlich sind.

Government delivery often fails before teams even begin, because procurement locks in assumptions and restricts flexibility. Shifting procurement left and adopting Lean-Agile Procurement creates faster, collaborative, outcome-driven contracts. By building commercial capability and integrating procurement into discovery, departments can finally buy learning, reduce risk, and enable true agility.

The Sprint Review is more than just a demo - it is a two-way communication to request feedback and learn from it.

I am often asked whether a Developer can support more than one Scrum Team. The answer is yes, but it's not ideal. Being on multiple teams means attending two (or more!) Sprint Plannings, two Sprint Reviews, two Retrospectives, and two sets of refinements. Not to mention two Daily Scrums—every single day.

The Anatomy of a Product explores products as living systems, revealing how to diagnose and improve every part, from vision to delivery. Using metaphors, practical tools, and real-world stories, it helps product teams think clearly, collaborate better, and build healthier, more purposeful products.

In diesem Artikel erklärt PST Simon Flossmann, wie Scrum Master ihre Product Owner bei der Maximierung des Wertes unterstützen können.

The article explains that psychological safety does not promote repeated avoidable mistakes but instead fosters transparency, learning, and responsible professional behavior. It highlights that teams with high psychological safety are more likely to openly discuss errors, leading to meaningful improvements rather than hidden issues.

81% of Singapore businesses use Agile, but 57% say their teams don't understand it. Discover the real cost of bad Agile implementations and how to spot the warning signs before it's too late.

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.

AI won't make product managers obsolete - but it will expose who has been doing real strategic thinking and who has been hiding behind administrative tasks. The future belongs to Cognitive Orchestrators who set intent, shape ethical constraints, and elevate decision quality - not passive reviewers of AI output.

With one Scrum Team, most people agree it’s easy to shape your Scrum in many ways. You can aim for innovation, efficiency, or customer-specific work. Just use different practices and it works. Once you add a scaling framework, that flexibility drops. The real optimisation goal shows up. Many times the focus is on: small batches, smooth flow, overlapping skills, standards, waste elimination, reuse. All very useful, but mainly about efficiency. ( Which is okay, actually in my experience it is what orgs want most of the time... efficiency and predictability! ) Those same ideas do not always help when you explore new products or co-create tailored solutions with customers. There, learning, experiments and customer-specific choices may matter more than waste reduction, avoiding duplication or efficiency. So what? Well, if it’s unclear what you optimise for, you might ask for innovation and customer focus, but design a setup mostly for efficiency. The result: strategy and org design become unaligned, and not so very good things happen. Now what? Be explicit about which one you’re really optimising for. And then look at the frameworks principles/mechanics and ask: What are these really trying to maximise?

Scrum Teams don’t start with every skill—they grow them. By sharing what they know and acquiring what they need, teams expand their collective intelligence and improve continuously. Whether it’s asking, buying, or working for new capabilities, growth is a team sport in Scrum.

Dieser Artikel zeigt Ihnen, wie Sie kulturelle Dysfunktionen diagnostizieren und entscheiden können, welche Auseinandersetzungen zu führen sinnvoll sind.

Despite a decade of digital progress, government still defaults to fixed-scope, output-driven delivery. An Agile Product Operating Model offers a structural fix, replacing fragile project teams with stable, outcome-focused product lines. With smarter funding, lighter governance and real product leadership, departments can boost resilience, value and supplier collaboration at scale.

How leaders can make organizational design a practical, everyday tool rather than a last-minute fix. With Org Topologies, you learn to see the real patterns shaping performance, involve people in designing meaningful change, and evolve your organization with purpose. It’s a guide for leaders who want clarity, adaptability, and results that last.

Most Scrum problems don’t come from the team at all. They come from a lack of real business engagement. In this blog, PST Robb Pieper explains why active leader involvement is the difference between stalled delivery and meaningful results. Download our guide to learn how to build the level of engagement Scrum depends on.