In Episode 12 of "Scrum is Hard and Disruptive," Todd Miller and Ryan Ripley discuss the importance of maximizing value by delivering only the highest value functionality, emphasizing the need to say "no" to unnecessary features.

In my previous post on Product Definition, which you can read here, I introduced the basics of how products—both internal and external—are defined in an agile organization. Today, I’m excited to share a deeper dive into this concept through a new video, where I walk you through how we apply Systems Thinking in the Creating Agile Organizations (CAO) approach.

Dans le monde compétitif du développement de produits, le succès n'est jamais garanti. Cet article explore cinq exemples flagrants d'échecs de produits, du Fire Phone d'Amazon à Quibi, en analysant ce qui n'a pas fonctionné et comment une validation adéquate aurait pu éviter ces erreurs coûteuses. Découvrez comment le cours Professional Product Discovery & Validation (PPDV) peut vous donner les outils dont vous avez besoin pour éviter de tels échecs et guider votre produit vers le succès.

The goal of a SM is to grow the teams to thrive, innovate, and deliver exceptional products. Understanding and embracing the various dimensions of the role can enhance the effectiveness of your team.

In this episode of the take5IRL podcast, PST Jeff Lee and his colleague Patrick Campbell take you behind the scenes of a transformative case study. They dive into the challenges faced by a struggling product group in the medical device industry. Faced with the urgent need for change, they turned to Agile, but how do you implement Agile in a regulated environment? Tune in to hear how our team at agilityIRL brought fast-paced, hands-on Agile training to this team, guiding them through a steep learning curve to achieve remarkable results.

In part 2 of this powerful medical device case study, our hosts, PST Jeff Lee and Patrick Campbell, continue the journey from where we left off in episode 62. After hands-on Agile training, we moved into coaching the team as they executed their first sprints. Tune in to hear about the cultural shift that took place—a big change for the company that allowed them to see improvement in real-time and track progress like never before. Curious about the results? Listen in to see the tangible improvements and what they were able to accomplish as they embraced Agile in a regulated environment.

How can we avoid people punting on Professional Scrum because it is "nice-to-have"? How can Product Market Fit thinking help us? How can we focus on demand via an internal case studies perspective?

In their latest episode, Todd and Ryan explain why Scrum is often harder than waterfall development, emphasizing that iterative processes require constant adjustments to engineering practices and architectural decisions. They highlight that Scrum forces teams to move away from over-planning and focus more on building and testing, which demands a disciplined and adaptive approach.

Las empresas que buscan adoptar Scrum podrían mejorar su uso y la obtención de beneficios si evalúan primero las diferencias entre el enfoque de producto en el cual se basa Scrum junto al enfoque ágil y el enfoque de proyectos, o modelo tradicional de gestión de proyectos para aprovechar mejor los beneficios. En el siguiente post explicamos algunas diferencias que nos permita adoptar de manera apropiada el enfoque de producto con Scrum.

Nel mondo competitivo dello sviluppo dei prodotti, il successo non è mai garantito. Questo articolo esplora cinque clamorosi esempi di prodotti falliti, da Amazon Fire Phone a Quibi, analizzando cosa è andato storto e come una corretta validazione avrebbe potuto prevenire questi costosi errori. Scopri come il corso Professional Product Discovery & Validation (PPDV) può fornirti gli strumenti necessari per evitare simili fallimenti e guidare il tuo prodotto verso il successo

In diesem Artikel stellt PST Simon Flossmann drei Arten von Scrum-Meeting vor, die jeder Scrum Master sicher moderieren können sollte.

Incremental delivery is the superpower behind the Scrum framework. Scrum is based on Empiricism, which requires Transparency, Inspection, and Adaptation. But none of that works without delivering value in increments.

When designing your own Agile framework, there’s no one-size-fits-all solution. The key is to find the right balance based on how work flows through your system, particularly focusing on the type and frequency of dependencies. Your framework design should prioritize eliminating the most common dependencies first.

The video emphasizes that Scrum is a simple, adaptable framework that doesn’t need enhancement, unlike complex methodologies. Instead of altering Scrum, teams should focus on adding context-specific practices and addressing organizational impediments that hinder progress. The key message is to improve the environment in which Scrum operates, not the framework itself.

In this article, PST Alex Ballarin explains how UX Design activities (e.g. discovery) can be effectively included in the Scrum events and artifacts using the dual-track agile approach, simultaneously with the software delivery work.

As a Scrum Master, solving problems for the team is acceptable for the right reasons. Don’t do it out of routine. Before solving a problem, consider if you’re helping the team grow in their ability to resolve similar problems independently.

A well-crafted Business Problem Statement is key to guiding your team toward the right solutions, rather than jumping to conclusions. This article explores how to create impactful problem statements by focusing on the "Why," "What," and "Who" behind business challenges. With real-life examples from e-commerce, healthcare, and publishing, learn how to foster creativity, empathy, and ownership in your team, while keeping your goals clear and aligned.

Is your team changing or skipping Scrum elements to cover up deeper problems? Learn how to identify what’s missing, uncover the real issues, and find better ways to leverage the Scrum framework for more effective results.

In the latest episode of "Scrum is Hard and Disruptive," Todd Miller and Ryan Ripley discuss how Scrum is not just a process to be implemented but a powerful tool to drive change within organizations. They emphasize that many companies misuse Scrum by treating it as another procedural rollout, failing to embrace its disruptive nature meant to challenge old business habits.

A roadmap is a visualization of the Product Owner’s plan to deliver the Product Goal and fulfill the product vision. But in the real world, especially in complex environments, plans change—and that’s okay.

„Es gibt nichts mehr zu verbessern.“ In diesem Artikel beschreibt PST Simon Flossmann 3 erprobte Formate, mit denen du als Scrum Master diese kritische Sprint-Retrospektive moderierst

Wie Mikromanagement, mangelnde strategische Transparenz, Geringschätzung von Teams und leichtfertiges Eingehen von Risiken die Gesundheit von Organisationen untergraben, Innovationen ersticken und im Widerspruch zu agilen Prinzipien stehen können.

Scrum est-il agile ? Découvrez comment ces concepts se croisent et ce qu'il faut vraiment comprendre pour éviter la confusion. Visionnez notre vidéo pour démêler les fils !

Todd and Ryan discuss the ongoing struggle of Scrum teams against ingrained Waterfall habits and predictive thinking that undermine Agile principles. Despite shifts in workforce generations and management styles, many teams still sacrifice quality to meet deadlines and rigid plans.

“OKRs S&%k, but we don’t know anything better” This was a direct quote from a cybersecurity scaleup’s Chief of Staff, but I hear the sentiment way too often from founders, chiefs of staff, COOs, and others in the scaleup ecosystem. I started encountering OKRs when working with scaleups a couple of years ago, helping leaders fix their ways of working to reap the promised benefits of “Agile.”

"We are a team providing services, why should we care about this new Product Operating Model?"

Scrum adoption requires top-down leadership but thrives with a “middle-out” approach that engages middle management to drive organizational change. Sustained effort and healthy conflict resolution are crucial, as the journey is ongoing and filled with challenges. To succeed, organizations must embed Scrum principles deeply enough that change continues effectively beyond the influence of any single individual.

Understanding the Scrum Master role is challenging for many people. One of the roles in other fields close to the Scrum Master role is Orchestra Conductor. Watch this video to perceive the Scrum Master role from a new angle.

A great Product Owner leads with vision, validates the value delivered and encourages experimentation and risk-taking, helping the team unlock new possibilities to focus on delivering value.

Is the role of Scrum Master really relevant when Scrum has become the norm while the Scrum Masters themselves have not really upskilled or reskilled to support the Scrum Teams.

In this episode of the take5IRL podcast, Jeff Lee and Kelly Weyrauch break down what the FDA expects from your systems and reveal how adopting an Agile approach can give your company a competitive edge. Don't miss out on these game-changing insights!

This blog post explores how Scrum's intentional pressure on both engineering and product management teams drives continuous improvement and excellence. It emphasizes the importance of the "Definition of Done" and the need to close the "Effectiveness Gap" between current and target practices. Ultimately, the stress Scrum creates is a positive force that helps teams achieve better outcomes with each sprint.

In 2022, Andrew Sales (Chief Methodologist and SAFe Fellow at Scaled Agile, Inc.) was talking at the Tecnifor SAFe Day. You can find the talk here. His subject was “accelerating flow of customer value”. I want to reflect on this talk and share how we can help improve flow of customer value in SAFe systemically. This post invites you to improve SAFe beyond the solutions proposed in this talk.   

This article delves into the darker aspects of Founder Mode, popularized by Paul Graham and others, offering a critical perspective for agile practitioners, product leaders, startup founders, and managers.

3 Tipps, wie ein agiles Mindset wissenschaftlich fundiert förderst.

The Scrum Master is primarily responsible for the Scrum framework and the empirical process underlying it. Sometimes, this may require making tough decisions. To what extent does this include removing people from the team? We share our thoughts in this article.

Looking to hire the perfect Product Owner? In this video with PSTs Robert Pieper, Jason Malmstadt, and Greg Crown, learn about the essential skills needed and discover how to avoid common hiring pitfalls.

Partial implementations of Scrum often obscure critical dysfunctions in product development, preventing teams from fully benefiting from the framework's potential. Scrum Masters are vital in identifying and addressing these issues, requiring experience and leadership to drive real change.

Is data always the key to successful product development? In this article, we explore when data collection helps and drives innovation, and when it can lead to misguided decisions or wasted efforts.

Developing your company's purpose is one of the most critical steps in building a meaningful and successful business. Gone are the days when work was solely about trading time for money. Today, employees seek a deeper sense of purpose, often valuing it more than financial compensation. In this blog, we explore the significance of company purpose, why it matters, and how to develop your company's purpose to inspire your team and create a basis for sound future decision-making.

Curious about how the Scrum Guide can be your team’s compass in navigating complex challenges?

Product discovery is not just a process — it’s a critical mindset for driving successful product development. By adopting a structured approach to discovery, teams can ensure they are solving the right problems and delivering value to both customers and the business.

Scrum is more than a project management tool; it’s a competitive advantage that exposes organizational weaknesses and drives continuous improvement. Todd and Ryan emphasize that while Scrum highlights inefficiencies, true success requires adapting and addressing these issues rather than ignoring them.

Teams can build a product or feature exactly to specification and still fail if customers don’t respond positively to the product. In their haste to deliver the teams don’t have the necessary information to understand what their customers and users want nor why, so they build.. something. This blog discusses and suggests ideas for readers to consider when using product discovery in their product management process.

In this blog, we dispel a series of myths associated with product discovery in Scrum. Myths such as “it's a phase in the process and can not be done in a Sprint,” “It's only for greenfield projects,” to “ The DoD stops us from doing Discovery”.

Discovery and validation should be an integral part of the work of a Scrum Team. It provides a collection of practices that enable Scrum Teams to drive an evidence-based approach to value.

Willst du als Scrum Master langfristig Karriere machen? PST Simon Flossmann erkläre in diesem Artikel wie es gelingen kann.

Möchten Sie Produkte in einer Weise entwickeln, die kostspielige Fehler vermeidet, die Kundenbedürfnisse erfüllt und Ihre Karriereaussichten drastisch verbessert? Dann ist das Pre-Mortem Ihre Geheimwaffe!

Découvrez 5 conseils essentiels pour réussir votre entretien de Scrum Master. Apprenez à vous préparer, à incarner les valeurs agiles, et à poser les bonnes questions.

Mechanical Scrum can become a trap when we follow Scrum without understanding Scrum. The Scrum framework is a great place to start in order to deliver value, but it shouldn’t be itself a destination.