Product Owners must know their customers to succeed in today’s competitive markets. There is a common agreement among experts involved in product management about it. A lot has been said about this topic. In this blog post, I discuss the different ways to know your customers. To make it more practical, I share some tools to ease application in the work environment.

In this video, Martin 🎥 delves deep into the essence of Scrum, highlighting its role not as a problem solver, but as a revealer. He draws a vivid picture, likening Scrum to a mirror 🪞. It reflects back to us the challenges and obstacles we face, making them visible so we can address them head-on.

The Scrum Master accountability extends far beyond guiding the Scrum team through Scrum events and facilitating meetings as requested or needed. Scrum Masters are change agents who transform not just the team, but also the entire organization.

Product Owners are accountable to provide stakeholders have a clear understanding of the product's direction. In this new episode of the take5IRL podcast, Jeff and Mike explore methods for enhancing transparency. Discover how providing transparency to the Product Backlog can foster a shared vision and facilitate meaningful collaboration with stakeholders.

Scrum Values make the use of Scrum successful. How can you and your Team live these values during the entire Sprint? Check it out!

How do you “implement agile” in an organization that has no experience with agile practices? Or does the phrase “implementing agile” even make sense? If agility is more of an outcome than something you do, how do you take an organization that is new to agility, and help them become more flexible and adaptable? PST's Robert Pieper, Gregory Crown, and Jason Malmstadt share their thoughts.

This blog explores the crucial role of a Product Owner (PO) in managing the Product Backlog. Through facilitation, a PO can enhance team and stakeholder understanding of the Product Backlog, turning it into a narrative that drives everyone towards a shared vision and product goal. We discuss how the skills of storytelling and workshop facilitation, underpinned by core facilitation principles, significantly improve a PO's ability to navigate through backlog management and stakeholder engagement.

🚀 Diving deep into the world of Story Points! 📊 Ever wondered about their true value and how they fit into the bigger picture of team performance? Dive into my latest article where I unravel this enigma. Let's journey together from the subjective realm of Story Points to the tangible metrics of throughput and value. 🔄💡 #Agile #Scrum #ValueDelivery

In this video, we delve into the pivotal role of the Product Owner in Scrum. Beyond just a title, the Product Owner embodies the accountability of maximising value, setting strategic direction, and ensuring alignment across stakeholders, customers, and the Scrum Team.

Wie ineffektive Zusammenarbeit auf der Ebene der Stakeholder oftmals zu einem ungeeigneten Berichtswesen auf der Grundlage falscher Metriken führt.

Heute hat Scrum.org ein neues Training gelauncht. In diesem Artikel findest du einen kleinen Vorgeschmack dazu:

Over time, various myths and beliefs have surrounded the concept of the Definition of Ready. What does it entail? It's all about the conditions that must be met for a Product Backlog Item to be considered ready for action and understood enough by the entire Scrum Team so that it can be pulled into the Sprint Backlog during Sprint Planning. While some embrace it enthusiastically, others avoid it like a burning flame. In this article, we aim to dispel any lingering doubts so that you can confidently decide "To use Definition of Ready or not to use."

La Gestión del Product Backlog (en inglés Product Backlog Management) es una de las habilidades más importantes que debe dominar un Product Owner.  El Product Backlog es una lista ordenada de todo el trabajo que se debe realizar para entregar el producto.  El Product Owner es responsable de garantizar que sea lo más valioso y completo posible.

The Daily Scrum can be reduced to a status meeting where likely a Scrum Board or a Burn Down chart is referenced perhaps… but do these tools help with transparency? They certainly can, but how are you using them? If your stakeholders and other product participants could know what the progress is at all times, this could be a game changer.

Teams tend to get in the nitty gritty details of expectations. A waste of valuable time. This blog posts provides a simple practice to start dealing with this.

The Product Backlog is an essential artifact in Scrum, but backlogs could be better for many teams. In this blog, we discuss introducing a new class, Professional Scrum Product Backlog Management - Skills, and how it provides learners with the skills necessary to improve their Product Backlogs.

How to develop trust through self-management, psychological safety and Transactional Analysis as tools for improving relationships and communication within the Scrum ecosystem.

In this article, we'll explore some popular tools and apps, including Jira, Team Foundation Server, Rally, and others, that Scrum Masters can leverage to help teams visualize their work, increase Transparency and increase team efficiency.

El refinamiento del Product Backlog es esencial para mejorar la entrega de valor. El refinamiento es una actividad continua que se realiza en cada Sprint balanceando la entrega de valor en cada con la proyección adecuada de refinamiento.

It's common for Product Owners to be concerned with keeping every idea on their Product Backlog until it's a delivered solution. But what if that idea has been there for 10 years… should it still remain? PST's Jason Malmstadt and Greg Crown give some ideas on how you can handle aging Product Backlog items.

Overmanaging a Product Backlog can be wasteful. Product Backlog Items are no guarantee of value so details should be added with the minimum amount of detail to perform the work.

In this video, we delve deep into the essence of Sprint Planning, shedding light on its pivotal role in Scrum. From understanding the Product Backlog to setting clear Sprint Goals, we explore how this process sets the tone for a successful Sprint and the importance of striking a balance between planning and delivery.

Discover how effective leaders can nurture team autonomy and decision-making capabilities by transitioning from control to collaboration through a structured mentoring process. Learn the key steps to empower your team and foster a transparent system for delegation.

Determining whether a Scrum Master is effective can be challenging, as their impact is often indirect and not always easy to measure quantitatively. In this article, we will explore key indicators that can help you evaluate the effectiveness of a Scrum Master.

What should Scrum Teams do with defects that are discovered? Do they belong in the Product Backlog? Would a separate list of bugs and defects be better? What approach helps with the transparency of the work? Learn how to handle discovered defects effectively.

Learn why ineffective collaboration at the stakeholder level often results in an unsuited reporting system based on misaligned metrics.

In this video, Martin delves deep into the intricacies of consensus in product development, highlighting its importance and the challenges it can present. 🎥🤔

Kennst du die Anatomie der Scrum Events? Dann wird dir die Moderation nicht schwerfallen. Die Anatomie im Detail erfährst du in diesem Artikel:

In this video, Martin discusses the tell-tale signs of a Product Owner who might be missing the mark. 🚫🎯 From products of poor quality or low value to inconsistent delivery, these are indicators that shouldn't be ignored. If a product owner is merely jotting down requirements without truly understanding or influencing the product's direction, it's a red flag. 🚩

Product Owners: have you been thrown into the deep end of the product management pool without a clear direction? Are you wondering how you can possibly begin to bring order to the chaos you’ve inherited? In this Scrum Lightning Round, PST's Greg, Jason, and Robb explore some key ideas and techniques to help you get started.

Découvrez le quotidien d'un Scrum Master ! Le guide Scrum n'est pas prescriptif sur ses taches? Plongez au cœur d'une journée type et démystifiez ce rôle essentiel. Si vous vous demandez réellement ce que fait un Scrum Master ou si vous souhaitez mieux comprendre sa valeur, cette vidéo est pour vous.

Scrum Values make the use of Scrum successful. How can you and your Team live these values during the Sprint Retrospective? Check it out!

Are you grappling with managing your Scrum Team's work? 🧐 We've got you covered! 💡 Our latest blog dives deep into the heart of Scrum Team operations. We help you demystify 🕵️‍♂️ two key aspects of Scrum: Sprint Work and Refinement. Discover how these tasks, though different, are two sides of the same coin, closely intertwined 🔄. Learn how to strike the perfect balance ⚖️, ensuring an efficient workflow and driving your project towards success 🏆. We also explore visualisation strategies with Azure DevOps, enabling you to manage Sprint work and Refinement like a pro. Gear up to unlock the path to project success with increased efficiency and streamlined processes. 💼🚀 Don't miss out on this opportunity to supercharge your Scrum Team! 🚀 #Scrum #Agile #ProjectManagement #SoftwareDevelopment #AzureDevOps #TeamWork #Productivity #Sprint #Refinement #ScrumTeam

A lot of Scrum Teams are struggling to get stakeholder engagement in their Sprint Reviews. Without the proper engagement from stakeholders, Product Owners run the risk of not properly adapting the Product Backlog. There are many different ways to spawn better stakeholder engagement. This article is going to focus on an aspect often not considered: who is invited.

La mentalidad de proyecto y la mentalidad de producto son dos enfoques diferentes para el desarrollo de productos. Primero, la mentalidad de proyecto se centra en la entrega de un producto o servicio en un plazo y presupuesto determinados. Por otro lado, la mentalidad de producto, por su parte, se centra en la creación de un producto o servicio.

In this video, we delve into the intricacies of Sprint Planning, highlighting common mistakes and offering insights on how to navigate them. From the importance of a well-understood product backlog to the perils of overcommitting, we explore the nuances that can make or break a Sprint.

A Management Metric With Unintended Consequences! 💀

Keine Idee, wie du die nächste Retrospektive gestalten sollst? Dann lies weiter:

Una transformación ágil es un proceso complejo, desafiante con muchos problemas que algunas veces se estanca debido a líderes que no maduran en la adopción del empirismo y hacen el cambio para resolver problemas complejos a través de la entrega de valor en ciclos cortos. Los líderes permiten el crecimiento o limitan el crecimiento de los equipos y la capacidad de ser ágiles en la organización. El evolucionar hacia un liderazgo que no use el control sino la autogestión para lograr resultados implica un cambio de mentalidad. Algunos factores o aspectos claves por considerar para convertirse en líderes ágiles serviciales pueden ser los siguientes:

Incremental delivery - or delivering value frequently - is a core concept of Scrum and yet it is so often misunderstood. Some might argue that it's wasteful to not make a few additional small changes or updates when you're already deep in the code. However, this perception is often rooted in a misconception. In reality, not using incremental delivery can be far more wasteful and inefficient.

It’d sure be nice if all the Stakeholders for a Scrum Team all agreed with the Product Owner on the direction for the product wouldn’t it? Or would it? Sounds kind of boring to us! Fortunately of unfortunately, Product Owners often have to navigate the challenges of working with Stakeholders who all hold different views on the direction of the Product. How do you manage this challenging situation? PST'S Jason Malmstadt, Robert Pieper, and I not only share some thoughts on this subject, but also a simple tool you can use with your Stakeholder crew!

Scrum is utilized in various industries, and as a result, leaders from diverse backgrounds are tasked with guiding Scrum Teams. While technical expertise can be an asset, it's not always a prerequisite for effective leadership in an Agile environment.

In this video, I, Martin, delve deep into the pivotal role of a Scrum Master or Agile Coach in motivating a Scrum Team. 📈🤝 I emphasise the importance of empathy, connection, and understanding the essence of a team's purpose. 🎯

Before going all-in on Agile, it's important to know the outcomes you want to achieve, the business value you want to create, and the leadership alignment you need to succeed.

La transformation digitale, suite à la transformation numérique démarrée il y a plus de 20 ans, a bouleversé notre quotidien. Cette révolution a bien évidemment changé de dimension avec l'avènement de nouvelles plateformes digitales, le cloud, le big data, l'omnicanalité, l'évolution de l'expérience utilisateur, etc. L'accélération et l'évolution des modes de consommation presque exponentielles dans leur adoption, en particulier en période de Covid, a complètement transformé l'horizon. Et comme Satya Nadella l'envisageait déjà en 2015, toutes les entreprises sont maintenant concernées par ces problématiques. La transformation est certes technologique, mais n'oublions pas que ce sont des humains qui sont à l'œuvre et que ces changements influent énormément sur les manières de travailler.

Does your Scrum Team find itself locked into destructive conflicts where each team member is convinced that their way is the only way, the best way and that everybody else who dares to disagree is crazy? Are you interested in shifting the dynamic from an "us vs. them" adversarial conflict to an "us vs. the challenge" partnership? What would be like if your team could harness every conflict to reveal new possibilities the team can align around? In this video, I will share an approach using the 10 Thinking Hats Of Scrum that can help your Scrum Team elevate the context of your conversations by evaluating options in the human-centric context of the people the Scrum Team exists to serve.

​​​​​​​We often get caught up in the tools we use and feel like we need to get our money’s worth by using every feature. Instead of creating transparency, using every feature of a tool often degrades the transparency of the Product Backlog. Keeping things simple and using a method such as a naming convention might be all that you need. Consider what is simple, is easiest to manage, and gives you the opportunity to create the most transparency.

Effective Sprint Planning is pivotal in Scrum. It hinges on ensuring the entire team grasps the Product Backlog, having a lucid product goal, and fostering a genuine team spirit. Without these, the path to building great products becomes muddled.

A 4-step approach to help you decide whether you should spend your precious and limited time on planet earth to use Scrum, bash Scrum or just move on with your life and ignore Scrum.

How much detail is enough? How much is too much? When it comes to Product Backlog Items, it can be challenging to find that “Goldilocks Point” of getting it “just right”. In this Lightning Round question, PST's Robert Pieper, Jason Malmstadt, and Gregory Crown tackle this issue with some disagreement among the group! Which one makes the most sense to you?