Someone asked us the question “How can we make Agile work with a long dependency chain?” With that as a somewhat-vague staring point, Jason Malmstadt and I explore ideas around Waterfall-Scrum Hybrid models, managing dependencies, and whether trying to combine these two ways of working even makes se...

In this vlog, join your hosts Andreanna Marshall, a professional Scrum Trainer at scrum.org, and the fantastic Scrum Master, Scott, as they dive deep into the Sprint Retrospective and provide several facilitation techniques to improve the event.

Scrum Masters are like great white sharks, if they stop swimming, they die. (Just metaphorically, thankfully.). Keep learning, Scrum Masters!

Most people familiar with Scrum know that teams need to break User Stories or other types of work into small pieces that can be done in a sprint. But this can be done in many ways. Are there ways that are better than others? Should you break it down by task? By area of expertise or specialization? P...

Going beyond autonomy, mastery & purpose. 10 intrinsic motivators that can help your team.

Watermelon metrics - reported green but in reality totally red. We've all seen them. But can we prevent them?

In this conversation on the Women in Agile podcast Stephanie Cully and host Emily Lint talk about the role of the Scrum Master. (36:57 Minutes)

This episode focuses on way to avoid robotic Scrum and make the Daily Scrum come to life!

In this article, we will explore some complimentary practices which the Product Owner might use to as an input when deciding how to order the Product Backlog.

“Administrative Overhead” is a phrase that strikes terror, anxiety, and boredom in the hearts of productive developers everywhere - including us at Responsive Advisors! In this Lightning Round Q&A session, PST'S Robert Pieper & Jason Malmstadt explore ways that Scrum can be used to lessen the amount...

Was sind Ideen-Sessions im Refinement, Sprint Reviews, Stakeholder-Meetings, Sprint Plannings und Sprint Retrospektiven wirklich? Es sind Entscheidungen. Mehr dazu in diesem Artikel!

How come? Learn more about nine reasons for this development.

SAFe puede ser bueno y te puede dar buenas cosas para tu organización. Veo mucho hate en muchos practicantes avanzados de agilidad en contra de SAFe. Si hay tantas organizaciones haciendo SAFe, será por algo.

What are the biggest reasons to use Scrum? What should a team or an organization expect to gain when implementing this framework? Why should anyone care? In this short Q&A session, PST'S Robert Pieper and Jason Malmstadt tackle the value proposition of Scrum, exploring the real, tangible benefits...

By understanding its customers and users, a Scrum Team can identify opportunities, be more innovative and create products that people need and use. Here are different techniques ways to do this.

Customer reviews are another way for the Scrum Team to gather feedback on the product. Reviews provide insights into what customers find useful, what they are struggling with, and what they don’t like. Reviews can be found in many places like the company website, social media, and on third-part...

An empathy map is a visualization tool that helps the Scrum Team get a better understanding of their user’s thoughts, feelings and experiences, so they can build and improve the product for their users. It is a technique used to create understanding and alignment. You can use an empathy map to coll...

One to one interviews are an easy way to gather insights. They can help the Scrum Team find out what their customers think about their product and what is important to them versus what is not. While conducting a one to one interview sounds straightforward, it requires discipline and practice in ...

Focus groups are a popular tool in market and user research. You can think of a focus group as a large scale interview as they typically consist between 5 and 10 users in a group. When running a focus group, the focus group moderator asks questions of the group and encourages discussion among th...

Surveys are one of the most common research methods and another way Scrum Teams can find more about their customers and users. For example, to determine customer satisfaction. Although surveys can be a cost effective way to gather data and insights from a large group of people, if they are not...

Evidence-Based Management (EBM) helps organizations work toward their goals in a complex environment. It focuses on measurable outcomes and desirable things that a customer or user of a product wants and experiences. EBM applies an empirical approach and serves as a foundation for Scrum Teams and or...

The Scrum Team should invite customers and users of their product to the Sprint Review. This is a perfect opportunity to engage with them to gather feedback and insight. Rather than using this time to dig into detail, focus on outcomes and gathering feedback and insight. Also, keep in mind that t...

By taking the time to observe users in their environment, you can learn a lot about how they interact with your product allowing you to explore how to make it better. During an observation session, ask users to interact with a lightweight prototype or observe them using the latest product Increm...

Product Owners are accountable for maximizing the value of the product that the Scrum Team builds. Therefore, as a Product Owner, you want everyone in the Scrum Team, including yourself, to have a shared understanding and be aligned on who the people are that would buy (customers) and use (users) yo...

A proto-persona is a fictional character based on what you currently know about the people that would buy and or use your product. Creating proto-personas collaboratively is a lightweight and quick way to build conversation and shared understanding within the Scrum Team about who they believe their ...

User role modeling is a lightweight way to categorize what roles users take when interacting with your product. Knowing these roles and how they impact how the user interacts with the product gives the Scrum Team more context when creating and refining their Product Backlog items, especially if ...

Thoughts and ideas on how to prevent, resolve, or simply accept it

Looking to get your team out of Mechanical Scrum (Zombie Scrum)? In this vlog, Professional Scrum Trainer, Andreanna Marshall teach esyou how to escape Mechanical Scrum and level up to Professional Scrum. Mechanical Scrum is a common approach to Scrum that can stop your team from developing and achi...

How does your Scrum Master supports adaptation in order to minimise deviations from agreed goals? Each of the Scrum Accountabilities has a role to play. So does the Scrum Master. Check it out!

In this episode Dave chats with PST David Sabine about his first experiences with Scrum and his journey to becoming a PST. (26:16 Minutes)

Coaching plays a pivotal role in guiding teams toward greater efficiency, collaboration, and overall success. It’s important to remember that you can't coach people out of every bad practice all at once. This article explores the wisdom behind focusing on the highest impact opportunities rather than...

At the heart of Scrum lies the Retrospective, a crucial event where teams reflect on their work and identify areas for improvement. One often overlooked opportunity at the Retrospective is measuring employee satisfaction. This article highlights the opportunity of incorporating employee satisfaction...

🔥 Navigating the Product Backlog just got more exciting! 🚀 Unravel why hierarchy might be your ship's anchor ⚓ in the stormy seas of complexity. 🔍 This article unveils the pitfalls of hierarchy and demystifies the complexities in product development. Learn how streamlining your backlog enhances inno...

Die Minimum Viable Library Product Owner Edition ist verfügbar! Entdecken Sie eine Reihe sorgfältig zusammengestellter Bücher, Newsletter, Podcasts und Tools, um Ihr Fachwissen zu erweitern.

In this Scrum Pulse webcast, PSTs Ravi Verma and Tony Lee share a simple, 9 step approach that they have started using to integrate the Co-Active coaching model into navigating resistance to Agile principles, values and practices.

Ser un Scrum Master efectivo que ayude a un equipo a ser exitoso puede tener sus complicaciones y llevar a un Scrum Master a mal interpretar la forma adecuada de ayudar y dar soporte. En este artículo presentamos tres errores comunes que muchos Scrum Master asumen.

Those newly introduced to the Scrum framework often have the same first question: What’s the difference between Scrum and traditional project management? Most people are familiar with the basics of traditional project management, so the question is a great place to start for understanding Scrum and ...

Anyone who is impacted by the outcome of the product and is interested in its success is considered a stakeholder. Examples of a Scrum Team’s stakeholders may include: Customers - users and buyers of the productInternal stakeholders - company management and other organizations such as Human Resource...

A core tenet of Scrum is that the Scrum Team receives rapid and frequent feedback from stakeholders in order to inspect and adapt its work. The entire Scrum Team is responsible for stakeholder collaboration, it is not just the Product Owner's responsibility. Scrum provides many elements that support...

While it’s important to understand who all of the Scrum Team’s stakeholders might be, not all stakeholders must be treated in the same way. Scrum Teams should engage with stakeholders in the ways appropriate for getting the feedback they need. For example, some of the stakeholders should regularly e...

Here are some common challenges Scrum Teams face when engaging with stakeholders and ways to overcome these challenges.

Scrum encourages frequent collaboration with stakeholders, and customers in particular. Understanding how to identify and learn about the challenges that key stakeholders face will help the Scrum Team better deliver the value they are seeking.

Jeff and Mike discuss guaranteed ways to make a Scrum Master fail. Do the opposite to aid in their success!

Here are some study notes that I created whilst learning more about Evidence-Based Management from Scrum.org. These are shared as a revision resource intended to summarise the key elements from The Evidence-Based Management Guide.

What is release planning? When is it done? How do we manage stakeholder expectations and answer the infamous "when will it be done" question? How do we forecast? What numbers and methods can we use to forecast more accurately?

Working virtually can be challenging when it comes to feeling you truly working as a team. This guest asked us what you could do or try to create a team feeling in a remote environment.

Explore a series of carefully curated collections of essential books, newsletters, podcasts, and tools to elevate your agile expertise.

Test which rules really matter and trigger a wave of change in your organization

Was kannst du von „Karl Klammer“ über Produktziele lernen?

Unleash Scrum's Potential: Discover Where to Start for Efficient Value Delivery (Product) and Continuous Improvement via Value Stream Mapping