Understanding the true nature of the Product Backlog is essential for the success of Scrum and the delivery of value to stakeholders. By dispelling common misconceptions and embracing this knowledge, teams can enhance their responsiveness, prioritize effectively, and deliver maximum value to their customers.

These questions can shift the focus from solutions and features, to value and utility - useful when a stakeholder's asking for a specific solution.

Transitioning from a traditional project manager to a Scrum Master involves moving from sole responsibility for project work and reliance on formal status reports to fostering a culture of team collaboration, shared ownership, and empirical progress tracking.

Ein Blick auf eine kaum genutzte Möglichkeit der Schaffung von Werten für Kunden und Organisation.

In diesem Artikel erklärt PST Simon Flossmann seine 5-Schritte-Anleitung die Scrum Master hilft mit "abwesende Product Owner“ umzugehen.

Understanding the role of Stakeholders in Scrum is essential for the success of any product. By dispelling common misconceptions and embracing the true nature of Stakeholder involvement, teams can foster more effective collaboration, improve decision-making, and deliver products that truly meet user needs and business goals.

In the late 90s, many companies adopted a 150-person rule for organizational units to maintain manageability and cohesion. However, this approach often led to fragmented products and complex management structures, making strategic execution a challenge. Today, a new idea is emerging. Instead of splitting units by size, companies are forming dedicated product groups with full P&L responsibility, encompassing entire product families. This shift has streamlined strategic units, reduced reporting lines, and enhanced agility in responding to market changes.

Louis-Philippe Carignan joins Matt Dominici to share some data that tells us we might be starting the clock to late in our efforts to measure Cycle Times.

Every Scrum Team wishes they had time each Sprint to accomplish more. By leveraging Artificial Intelligence (AI), teams can get that time back and become more effective. AI is revolutionizing various industries, and its potential to enhance how people and teams work is becoming increasingly evident.

One of the accountabilities that a Scrum Master has to fulfill is to make the Scrum Team effective. This includes the Scrum Master, as well. However, in my experience I have come across only a handful of Scrum Masters who understand the concept and who focus on improving and making themselves effective. If as a Scrum Master one does not focus on making themself effective they might not be able to help the team to become effective.

En este artículo, el PST Alex Ballarin explica qué beneficios tiene añadir los OKR al muro de producto del Equipo Scrum, y como utilizarlo para el centro de las conversaciones en los eventos compartidos entre Scrum y OKR.

Understanding the true role of the Product Owner is crucial for the success of Scrum teams and products. The Product Owner is not a traditional manager or a taskmaster but a value maximizer, visionary, collaborator, and customer advocate. By dispelling these misconceptions and embracing the true nature of the Product Owner, teams can foster a more effective and productive environment for product development.

Agile Teams as Investors: A Deeper Dive into Maximizing Organizational Value by Trusting Your Teams to Find Solutions to Your Customers Problems.

Effective stakeholder management is crucial for a successful product. By understanding their perspective, focusing on their success, and slowing down to bring them along, you’ll significantly improve your communication and collaboration. Remember, it’s about creating a shared vision and journey, not just pushing your agenda.

A myth re-visited. Seven years ago, Christiaan Verwijs and I wrote the article "The Scrum Master is a Junior Agile Coach" and explained why this is a myth according to the Scrum Guide. What's the state of this myth today?

In diesem Artikel erklärt PST Simon Flossmann, was du tun kannst, wenn du in der Sprint Retrospektive in Zeitproblem kommst.

While there are various ways to write or format items on the Product Backlog, one of the most popular and effective methods is writing them in the user story format. This practice, though beneficial, is not mandatory. Scrum teams may choose to adopt the user story format when it suits their needs and enhances their workflow.

Some teams think that if they skip refinement, they're saving time, but that's not true at all. Teams must understand what is needed before they can deliver value. Refinement will happen. It's just a matter of whether it will be done in Sprint Planning, during the Sprint, or whether you will do it in advance of the Sprint as part of regular, planned refinement activities.

このポッドキャストでは、業界のエキスパートを特別ゲストとして迎え、アジャイルとスクラムの世界にふかく潜り込んでいきます。スクラム、DevOps、ユーザーエクスペリエンス、プロダクトマネージメント、コーチングなど、様々なトピックをカバーします。私、フォンテーヌグレゴリは、「アジャイルの旅」ポッドキャストのホストです。アジャイルコーチ、スクラムマスター、またはコンサルタントとして日本企業を支援しております。そして、Scrum.orgの認定プロフェッショナルスクラムトレーナーです。 今回のエピソードのゲストは株式会社ITプレナーズジャパンアジアパシフィックの原秀文さんです。 DX、DevOps、アジャイル開発の導入に関する原さんの仕事について話しています。バリュー・ストリーム・マッピング(VSM)の多くの利点、ベンダーと協力してアジリティを支える働く方法、そしてDX・DevOps・アジャイル開発の導入の成功・進捗の測定方法について話し合います。

Understanding the Scrum Master's true accountability is crucial for the team's success. By dispelling these misconceptions and embracing the Scrum Master's true nature, teams can foster a more supportive and effective environment for product development.

Cosa vuol dire che uno Scrum Master è agente del cambiamento? In questo articolo, Fabio Panzavolta condivide la sua esperienza. Usare Scrum per rivelare ciò che rende l'azienda (o il team) meno agile per poi aiutare tutti, in azienda, a migliorarsi continuamente. Gli ostacoli che si presenteranno nel percorso di creazione del prodotto, saranno rimossi. Questa rimozione porterà più business agility: prodotti di migliore qualità, clienti e dipendenti più contenti, più rapidità per andare dall’idea alla produzione.

Organizations can foster a more productive, innovative, and responsive work environment by recognizing what a Scrum Team is Not and embracing what it truly is. What kind of Scrum Team do you have? Pick your favorite from the list.

Transitioning from a traditional project manager to a Scrum Master requires embracing shorter planning cycles that focus on continuous adaptation and stakeholder collaboration, moving to flexible, outcome-oriented approaches that enhance team agility and responsiveness to change.

El Product Owner tiene la responsabilidad de maximizar la entrega de valor. Esta responsabilidad puede requerir desarrollar una variedad de competencias y habilidades como son: Liderar hacia el valor, Involucrar en la visión, y evolucionar el producto con la validación a través de un enfoque incremental y empírico. En esta entrada se muestran algunas de las competencias requeridas.

The implementation of an agile lean change approach is easy to talk about, but harder to execute. By focusing on incremental change, frequent feedback, and tailoring the approach to specific needs, Agile enables businesses to respond effectively to evolving markets and deliver greater value.

Product Managers and Product Owners often find themselves caught in the delivery drain, where their time and energy are consumed by the operational aspects of getting a product out the door. This focus on delivery not only drains their resources. But also forces them to operate on an operational level, leaving little room for the strategic and tactical thinking that drives real product innovation. To truly excel, product teams must shift their attention to product discovery. A critical yet frequently overlooked aspect of product management.

In diesem Artikel beschreibt PST Simon Flossmann 3 kreative Methoden zur Rettung deiner Scrum-Master-Community-of-Practice

In their discussion titled "Scrum is Hard and Disruptive #2 - Complexity and Risk," Todd and Ryan explore how Scrum optimizes product management by emphasizing high-value delivery. They emphasize that while Scrum is designed for high-risk, complex projects, its success hinges on consistent product releases and iterative feedback loops to manage risks effectively.

Feeling overwhelmed as a Scrum Master? Don't try to do everything at once! This post offers a simple, iterative approach to focus your efforts on the most impactful areas, helping your team achieve greater results.

In the ever-evolving landscape of project management, Scrum has emerged as one of the most popular frameworks for Agile development. Despite its widespread adoption, many misconceptions exist about what Scrum truly entails. Understanding the essence of Scrum is crucial for teams and organizations to harness its full potential and achieve their goals efficiently.

A former student of mine asked me a question: I've just started working with a product development team whose members live in India Standard Time, Central European Time, and East Standard Time I'd like to help to configure our Sprints. Do you have advice about stand-ups? How often? Should we meet later in the day? Any advice would be appreciated.

It is rare that teams get the full value that they should from their Sprint Reviews. We and others have experienced Sprint Reviews more as performance reviews or demos that feel like one-way presentations from the team. The opportunity for Scrum Teams and their stakeholders to explore the current and potential value of products, market insights and technology trends that could be leveraged is often missed. In this blog, in collaboration with Patricia Kong and Glaudia Califano, I share different ideas, challenges and facilitation techniques to help you and your teams have more effective Sprint Reviews.

“A product is a vehicle to deliver value. It has a clear boundary, known stakeholders, and well-defined users or customers. A product could be a service, a physical product, or something more abstract.” - The Scrum Guide

Discover how Max, an AI agent, integrates into Adrien's Scrum Team, enhancing productivity and bridging skill gaps. Uncover the groundbreaking music and clip generation product they are developing together. Explore the opportunities AI agents like Max bring to agile teams, and reflect on the insights from AI safety researchers Diego Dorn and Alexandre Variengien about the potential limitations and risks. Delve into the intriguing question: Is Max loyal?

This blog answers the questions that we did not have time for in the webcast on Procurement and Supply in Agile Transformations. There are many challenges that are common in introducing agility into Procurement and Supply that have been observed within agile transformations.

In diesem Artikel beschreibt PST Simon Flossmann die 5 schlimmsten Anti-Pattern für Sprint Reviews.

Despite its widespread adoption, Agile is often misunderstood and misapplied. Many still hold onto traditional project management views, leading to confusion and ineffective implementation of Agile practices. To truly harness the power of Agile, it's essential to understand what Agile is not and what Agile is. Find out more about what Agile is and is not in this post from Sanjay Saini.

What does product success mean? In this energizing Hands-on Agile Meetup, David Pereira talked about the challenges of being a product manager and how to move from managing the Product Backlog to driving value.

A professional use of the Scrum framework is not about “doing” Scrum, it is about living a number of foundational concepts. Check it out! Back to the foundations of the Scrum framework (78)

In this VLOG, Matt speaks with Adam Bullied, COO at Circus about his experience implementing Flow Metrics in a Startup Environment

Story points could be a great tool when combined with planning poker for getting estimation related conversations started. However, there has been quite a backlash and debate on whether to use story points or not.

In diesem Artikel verrät PST Simon Flossmann 3 folgenreiche Fehler, die Scrum Trainer unbedingt vermeiden sollten.

Wie Sie sich vorbereiten können, um sich als Kandidat zu profilieren

In this video, Todd and Ryan explore Ken Schwaber's 2006 white paper, which discusses why Scrum is hard and disruptive. They use cross-functional, self-managing teams to emphasize Scrum's foundation in iterative and incremental development. Lean thinking and empirical process control are core principles, ensuring continuous improvement through frequent inspection and adaptation. The hosts draw parallels to real-life scenarios, like youth football coaching, to illustrate the effectiveness of self-managing teams.

Agile can be confusing, and Agile Myths can really impact an organisations performance. Learn about the common myths here and avoid them!

No mundo dinâmico do desenvolvimento de produtos, a descoberta contínua, termo criado por Teresa Torres, é essencial para garantir que os produtos atendam às necessidades dos usuários e ofereçam valor. Este artigo explora como integrar práticas de descoberta contínua na estrutura Scrum pode melhorar o desenvolvimento de produtos.

Surfing can teach us a lot about enabling business agility. Learn 4 key strategies for continuous improvement and adaptability in unpredictable environments.

Velocity is a popular tool that many Scrum Teams use to size and forecast work. But so many organizations equate "velocity" to team "performance", and that is not what it's for.

En este artículo, el PST Alex Ballarín te explica como las métricas de producto son el corazón de los paneles de producto, donde el equipo puede compartir y alinearse respecto a la información importante del producto, y mejorar así su toma de decisiones.

In diesem Artikel erklärt PST Simon Flossmann, wie Product Owner in 6 Schritten Nein sagen können.