The 15-Minute AI-Enabled Prep for Scrum Masters and Agile Coaches to Build Trust

In diesem Artikel beschreibt PST Simon Flossmann 7 Eigenschaften erfolgreicher Scrum Master.

We are taught to chase certainty, but that leads to poor leadership. What we really need is to reorient ourselves towards clarity.

People often reach out to me — they're trying to decide whether to take a Scrum course or a Kanban course.

Frequent organizational restructuring disrupts careers, impacts morale, and affects business performance. Are leaders considering the human cost of constant change? Explore the effects of leadership transitions and restructuring in this insightful analysis.

Scrum is designed to help teams solve complex problems, but how do you determine if it’s actually working? Learn the key mistakes teams make when evaluating Scrum and how to measure its real impact before making changes.

PSTs Robert Pieper, Greg Crown, and Jason Malmstadt discuss why a clear product definition is key to success. They break down practical ideas to get it right, based on their real-world experience.

Ever felt like team conversations spin in circles? Mark cuts through the chaos, revealing the art of facilitation as a powerful tool for driving effective collaboration. Discover the four-phases—Context, Diverge, Converge, and Action—essential for guiding productive conversations and driving teams towards shared goals. Through practical techniques, you will be empowered to master facilitation and unlock the collective potential of your team.

The Product Owner role is evolving rapidly with the integration of artificial intelligence. As we move further into 2025, we're witnessing the emergence of AI-powered Product Owners who can deliver more value with less effort.

In diesem Artikel teilt PST Simon Flossmann 3 Wege, wie du Schulungen interaktiv starten kannst.

In the fast-paced world of leadership and career growth, the right guidance can make all the difference. But are you seeking coaching when you actually need mentoring—or vice versa? Coaching helps unlock your potential by guiding you to your own solutions, while mentoring provides wisdom and strategic advice from those who’ve walked the path before you. This article breaks down the key differences and real-world applications of both, helping you make informed decisions to accelerate your success. Whether you’re looking to grow as a leader or support others in their journey, understanding when to choose coaching or mentoring is the key to unlocking greatness.

Die Kosten für das Experimentieren sind gering, der potenzielle Karrierevorteil hingegen ist beträchtlich. Ein Grund, die generative KI in Agile zu verinnerlichen?

Scrum Masters, Agile Coaches, and others pushing for a more agile product organization often face apathy, resistance, or downright hostility from management. In this video, PSTs Jason Malmstadt, Robb Pieper, and Greg Crown break down why management often resists Scrum and share practical tips to tackle that pushback and make Agile stick.

Ever feel like your product organization is stuck in the mud... You’re not alone. Many teams start strong, laser-focused on delivering value and achieving product-market fit. But as success scales, things get messy.

What structure do the AI teams follow in Uber, Meta, or Spotify? I researched it and was able to find some articles and blogs from different people. This information may have changed, so please comment and provide references if you have access to the latest information. Happy reading!

This is a story about a former client. Early plans were to release a “Minimum Viable Experience” before year end. By late Spring, the Product Director described two “problems” and asked for my help: Release dates for the first publicly available version were slipping. And scope was expanding.

This podcast series aims to explore the latest market trends, introduce AI tools for Agile Teams, share AI tips and tricks, and raise awareness among Agile practitioners about AI's capabilities.

Some teams are obsessed with documenting everything. They create tickets for tracking time, logging meetings, or even planning how to plan. They think they’re being transparent. In reality, they’re just adding layers of clerical work that don’t actually help deliver value.

Implementing change in the workplace is one of the most crucial skills in your professional career. Regardless of your current position and industry, with high probability, your next big step in professional growth will be related to change. This article is worth reading if you want to be more effective in implementing change in the workplace.

In diesem Artikel erklärt PST Simon Flossmann welche 7 Fragen sich Scrum Master in den ersten 90 Tagen unbedingt stellen sollten.

The cost of experimentation is low; the potential career advantage, on the other hand, is substantial. A reason to embrace generative AI in Agile?

Over the years, I've noticed recurring challenges and red flags that can seriously limit Scrum's effectiveness. Spotting these symptoms early can mean the difference between Scrum thriving or turning into "mission impossible." In this blog post, I'll highlight the key pitfalls to watch out for.

Scrum Masters can sometimes fall into the trap of managing the process rather than coaching the team. While it might seem helpful to update tickets, close backlog items, or move tasks around, this kind of administrative work actually disempowers the team and takes the Scrum Master away from their real job: helping people grow, removing obstacles, and improving the adoption of Scrum.

Using velocity to measure the success of a Scrum team is like measuring a machine by a single cog in the wheel. The cog may be important, but it’s not the same as the value the machine produces.

New tools, frameworks, and best practices seem to appear every week—and many organizations adopt them without stepping back to ask a simple, but critical question: Does this support the way we compete? At the heart of good companies is a clear strategy—how you create value in the market. While there are many variations, most organizations compete along one of three fundamental value dimensions

How do you develop your company/operating model using product techniques? How do you use an Agile Product Operating Model to build your Agile Product Operating Model? Here's a somewhat concrete playbook bringing this thinking to life.

Implementing an AI transformation demands rethinking traditional organizational structures. Successful AI teams require autonomy, flexibility, iterative practices, and extensive cross-functional collaboration. This AI-driven organizational model balances strategic coherence, rapid experimentation, and continuous learning—setting the foundation for successful, scalable AI transformations.

Many teams struggle with Scrum—not because it doesn’t work, but because they modify it too soon. Before tweaking the framework, ask yourself: Have you truly tried Scrum as designed? Discover why ‘trying it as is’ matters and challenge your team to commit to five full Sprints before making changes.

Should all of the tasks be assigned in sprint planning and by whom?

Explore the relationship, differences and synergies between 3 Product-related buzzwords - Product-Led Growth, Product-Led Org, and Product Operating Model.

Selbstorganisation ist das Herzstück agiler Methoden wie Scrum. Sie ermöglicht es Teams, schneller und direkter Entscheidungen zu treffen, das Engagement der Teammitglieder zu steigern und den Bedarf an externer Steuerung zu minimieren. Doch was macht Selbstorganisation so effektiv? Und welche Voraussetzungen müssen erfüllt sein, damit sie ihr volles Potenzial entfalten kann? In meinem Blog-Post beleuchte ich die Schlüsselbedingungen für erfolgreiche Selbstorganisation: von klaren Zielen und Transparenz über das Vertrauen des Umfelds bis hin zur Integration des Product Owners als aktiver Teil des Teams. Entdecke, wie dein Team durch Selbstorganisation flexibler, engagierter und effizienter arbeiten kann!

In diesem Artikel erklärt PST Simon Flossmann 3 Denkfehler, die dein Sprint-Review ruinieren

Inspect & Adapt: Vibe Coding für schnelles Prototyping nutzen und gleichzeitig strenge Standards für den Produktionscode beibehalten? Oder es doch lieber beim Copilot belassen?

My two AI friends have read the first 3 chapters from the beta version of my book, Leading with Impact! In this BookCast, they talk about what they learned and how you might apply it as a Product or Technology leader who has taken on a new challenge - a new role, a new team or even an entirely new company. Think of yourself as being a fly on the wall at a book club meeting, where the attendees have actually read the book.

Transformation isn’t just about adopting new tools—it’s about rethinking how we work, collaborate, and create value. Through my journey coaching leaders and teams, I’ve seen what truly drives lasting change. It’s not a step-by-step process but a dynamic, interconnected journey. Where does transformation feel the hardest in your organization?

Many people think innovation and invention are the same—but they’re not. While invention creates something entirely new, innovation transforms what already exists into something better, smarter, and more impactful. Companies like Apple, Netflix, and Uber didn’t invent their industries, but they redefined them through innovation. So, what truly drives success—bold inventions or strategic innovations? And where does AI fit in this equation? Let’s dive in.

Learn why succeeding with vibe coding requires a balanced approach: use it for rapid prototyping while maintaining rigorous standards for production code, with developers evolving from code writers to architects and code auditors.

In diesem Artikel erklärt PST Simon Flossmann die 3 größten Refinement-Probleme

How "Strategy Knotworking" turns ideas and ambitions into reality, and why it's an excellent structure for your Sprint Retrospective.

Many organisations continue to struggle to adopt Scrum successfully as a framework for delivering great products. This post discusses some of the topics that these organisations have struggled with. The irony is that the elements of Scrum that they challenge are the very elements that can help solve their challenges.

This blog explores why traditional project management methods fall short in AI initiatives and how adopting an Agile mindset can significantly enhance AI success.

Scrum is described as ‘simple,’ but many teams still struggle. Why? Because simple doesn’t mean easy. Mastering Scrum requires discipline, collaboration, and continuous learning. Explore what ‘simple’ really means in Scrum and how to make it work effectively.

AI isn't just a futuristic concept—it’s already saving lives. My colleague Eric experienced this firsthand when his Apple Watch detected an irregular heartbeat, urging him to seek medical help. Before AI, such silent health risks often went unnoticed until it was too late. But today, with powerful machine learning models fueled by massive data, cheaper storage, and advanced processing power, AI is revolutionizing healthcare. From early disease detection to real-time monitoring, it’s changing the game. The question is—are we taking full advantage of it? It’s time to embrace AI for our health and well-being.

What is the Product Owner accountable for? From the Scrum Guide: The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. The important part to focus on here is - maximizing the value of the product. But how does the Product Owner know that they are really maximizing the value of the Product? Well, that is where Dan Olsen’s Product Market Fit and Evidence-Based Management from Scrunm.org becomes helpful.

Scrum gibt klare Strukturen vor, aber das Konzept des „Flow“ fehlt—und genau hier setzen die „3 Ways of DevOps“ an. Flow, der reibungslose Fluss von Arbeit, ist entscheidend für die Effizienz und den Erfolg in der Softwareentwicklung. Die drei Wege von DevOps bieten wertvolle Perspektiven, um Bottlenecks zu identifizieren, Feedback-Schleifen zu verstärken und kontinuierliches Lernen zu fördern. Indem Scrum-Teams diese Prinzipien anwenden, können sie nicht nur ihren Flow optimieren, sondern auch ihre gesamte Arbeitsweise verbessern und mehr Wert für den Kunden schaffen. Erfahre in meinem Blog-Post, wie DevOps den Scrum-Prozess bereichern kann und warum Vertrauen und Sicherheit der Schlüssel zu echter Innovation sind.

In diesem Aritkel teilt PST Simon Flossmann seine 3 liebsten Formate für persönliche Retrospektiven

Ein strukturierter Ansatz zur Nutzung von KI-Modellen, der eigens für agile Praktiker entwickelt wurde.

Unlock the transformative power of AI by turning your company's untapped data into groundbreaking market opportunities. This blog delves into how AI goes beyond automation, enabling businesses to reshape industries and create new revenue streams. Discover real-world examples—such as Amazon's predictive shopping and GE's maintenance strategies—that highlight AI's potential. Learn actionable steps to integrate AI into your business strategy, starting with identifying hidden data opportunities and fostering a culture of experimentation. Embrace AI as a strategic asset to gain a competitive edge in today's rapidly evolving landscape.

Don’t let poor Product Ownership cost your business valuable time, money, and talent. In this post from PST Sanjay Saini, he explains why your teams—and your bottom line—will thank you for training your PO.

Scrum als Phrase ohne Substanz Oft wird Scrum nur oberflächlich eingeführt: Meetings heißen plötzlich „Daily Scrum“, klassische Projektzyklen werden zu „Sprints“ umbenannt – aber inhaltlich bleibt alles beim Alten. Die Erwartung: Agilität soll die Geschwindigkeit und Effizienz steigern. Doch ohne eine echte Veränderung der Unternehmenskultur und Arbeitsweise bleibt Scrum ein leeres Versprechen.