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?

Il Podcast Scrum 🇮🇹 esiste per aiutare tutti coloro i quali vogliono imparare o migliorare la propria conoscenza di Scrum Professionale. In questo episodio, della serie "a domanda risposta", esploro quali sono le modalità per prendere decisioni in Scrum.

Just finishing several Product Backlog Items, without any clear reason why, is not a usable goal. Then what is? Find out in this video!

How the Agile Manifesto Was Created

7 Tipps, wie dir „Reading the room“ auch in Online-Meetings gelingt

Hacer la Daily bien es uno de los retos más grandes que tienen las organizaciones que hacen Scrum. La Daily Scrum, a menudo la mal llamada “stand-up meeting” o “reunión diaria de pie”, es uno de los eventos clave en Scrum. Su objetivo principal es fomentar la comunicación, la colaboración y la transparencia dentro del equipo de desarrollo.

In this video, Martin delves into the challenging decision-making process of whether to pivot or stay the course in a project. 🔄🛤️ He highlights the importance of balancing persistence with the recognition of when a change in direction might be more beneficial.

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

Scrum.org introduces Immersion Training, a unique alternative to traditional 2-day courses. It offers a flexible format with short sessions over weeks, promoting practical learning through real-world application and guided reflections for skill improvement. Immersion classes have the same learning objectives as their corresponding versions in the traditional setup. So what do they bring? Curious if this new format suits your needs? Read on for a list of compelling reasons why choosing an Immersion class could be the ideal decision for you.

🍵 As I sip my morning cuppa, I find myself deep in thought about the state of organisational agility. 🔄 I've seen methodologies rise and fall, each promising to be the magic bullet for organisational woes.

The Sprint backlog, a cornerstone of Scrum, offers teams a transparent view of their current work and progress. It's essential to differentiate between the Sprint goal and the Sprint Backlog, ensuring that teams set achievable goals while maintaining flexibility to adapt to changing needs.

Wie du Workshops beendest, damit sie noch lange in Erinnerung bleiben

Ihre Ursachen und wie Sie diese überwinden, z. B. durch empathisches Zuhören oder Mitgestaltung des Veränderungsprozesses.

If you are a Product Owner (PO), you are essentially the owner of the product and most POs I come across know what that entails. However, I also meet POs who determine during the Sprint which items from the Sprint Backlog the Development Team should work on, or what the solution should be, or even perform code reviews and evaluate work this way.

"How do you define Done when you’ve got dependencies outside the Scrum Team?” Dealing with Dependencies can throw a wrench into the process of even the most well-oiled Scrum Teams. It can be very challenging to get to a Done Increment when there’s something the team is depending on coming from outside the Scrum Team. How can a team best define Done in this scenario? PST'S Jason Malmstadt, Robert Pieper, and Gregory Crown have some surprising answers to this difficult question.

In this Scrum Lightning Round, our team tackles a very challenging question: “How does a Scrum Team work when they’re dependent on vendors or other business units that don’t use Scrum?” It’s a common scenario when applying Scrum in the real world and a question we get asked often. PST's Jason, Robb, and Greg all offer slightly differing perspectives on working through this tough situation.

The Scrum Guide is rather vague about how Product Backlog Items should be structured and how to make them transparent. That is by design because Scrum is intentionally incomplete. Understanding what attributes you are dealing with is helpful in creating a well-structured Product Backlog.

🚀 Dive into the world of empiricism in Agile development! 🌍 Discover how inspecting and adapting, deeply rooted in Agile practices like Scrum, ensures organisations stay ahead of the curve. 🔄 Join me on this journey through the Scottish Highlands of Agile development 🏞️, where change is the only constant, and success is all about reflection and adaptation. 💡 #AgileInsights #ScrumMastery 📊🔍.

One question that often arises in the context of Scrum is whether individuals can be part of more than one Scrum Team. While there is no explicit rule against this in Scrum, it's essential to explore the implications of such arrangements on productivity and adherence to Scrum values.

We have seen many Scrum teams attempt to resolve challenges by giving up and moving to Kanban. However, the decision to switch from Scrum to Kanban typically arises not from Scrum shortcomings, but rather from challenges in its implementation. In this episode, Jeff and Mike explore misguided reasons to move away from Scrum and things to consider before making that move.