Maryse Meinen: Value Over Velocity, A Product Owner’s Journey to Value-Driven Development, NoEstimates Unplugged Week

This is one of a series of episodes where Product Owners explain how they used, and benefited from #NoEstimates in their work with teams. 

To know more about #NoEstimates, sign-up to get the first 3 chapters of the book here.

Introduction to #NoEstimates

Maryse Meinen shares her journey into agile and lean methodologies, highlighting a pivotal moment at her first international conference where she attended a workshop on #NoEstimates led by Seb Rose. The workshop's quiz on estimating the distance from Earth to the moon led her to an epiphany about the common tendency to provide estimates even when uncertain, driven by peer pressure—an insight that spurred her to experiment with the #NoEstimates approach.

A Real-World Example of Success

Maryse describes her experience with a new team tasked with developing an infrastructure solution without relying on traditional estimates. By focusing on conversations, card confirmations (the 3 C’s of User Stories), and refining story points to either 1 or 0 based on whether a story was refined, the team managed to prioritize work more effectively. The practice of making items as small as possible and focusing on delivering value in various forms proved to be beneficial.

Challenges in Implementation

The biggest challenge in implementing #NoEstimates was not from management or stakeholders, but rather from inexperienced scrum masters resistant to deviating from traditional estimation techniques. Maryse found success by allowing the team space to operate independently and focusing on outcomes rather than estimates.

Impact on Planning and Prioritization

Shifting the focus from estimates to value delivered led to a significant change in how Maryse's team approached planning and prioritization. By setting sprint goals around solving real problems for real people, the team moved away from a task-centric to a value-centric approach. One of the core tenants of the #NoEstimates approach.

Measuring Progress Without Estimates

Maryse's team measured progress by the problems they solve, framing sprint goals around these problems and communicating achievements in terms of value delivered to stakeholders, rather than in traditional estimation-driven progress metrics, like tasks completed - which would not necessarily deliver any value to end-users and customers.

Advice and Resources for #NoEstimates

Maryse encourages teams to start experimenting with #NoEstimates and emphasizes the importance of continuous learning and adaptation. She recommends engaging with the #NoEstimates community on Twitter and exploring resources by Allan Kelly and Seb Rose, as well as the NoEstimates book.

About Maryse Meinen

Maryse is an Product Owner dedicated to fostering experimentation, agility, and empathy within organizations. She builds and facilitates great teams, coaches leaders, and believes in simplicity and human-centric methodologies. With expertise in Lean/agile development and a passion for teaching, she shapes adaptive and learning-focused cultures.

You can link with Maryse Meinen on LinkedIn.

Luis Garcia: Forecast Over Estimation, How To Transform Your Approach To Project Management, NoEstimates Unplugged Week

This is one of a series of episodes where Product Owners explain how they used, and benefited from #NoEstimates in their work with teams. 

To know more about #NoEstimates, sign-up to get the first 3 chapters of the book here.

Introduction to #NoEstimates

Luis Garcia, transitioning from estimation discomfort to a #NoEstimates approach as a product owner, discovered its benefits after attending a workshop by Woody Zuill. Faced with the challenges of hard commitments in government projects, he sought to shift focus from when to what and why in project discussions.

A Transformative Project Example 

Implementing #NoEstimates in a kanban team, Luis emphasized work breakdown and comfortable task sizing. This method facilitated stakeholder communication, improved expectation management, and enabled precise progress measurement through metrics like cycle time and using techniques like Monte Carlo forecasting.

Overcoming Implementation Challenges 

When Luis tried to introduce #NoEstimates, he originally faced skepticism, misconceptions about planning, and stakeholder resistance. In those cases, Luis advises focusing on forecasting based on available data, ensuring team stability, and managing expectations effectively. And focusing on progress transparency, instead of trying to change people’s minds.

Strategic Stakeholder Management 

Successfully integrating #NoEstimates involved fostering team accountability and ownership over the refinement process, thereby enhancing stakeholder dialogue and planning efficiency. For example, Luis shares that #NoEstimates shifted the team's focus to identifying and preparing the most valuable tasks, leveraging data for all planning and prioritization decisions. This focus helped to keep stakeholders informed, and improved transparency.

Measuring Success and Communicating Progress 

Without traditional estimates, Luis's team adopted a probabilistic approach to measure and communicate progress, supported by insights from the book "Thinking in Bets" by Annie Duke.

When it came to adopting a different way to measure and communicate progress, practicality was key; even simple tools like Excel were effective for data management in the #NoEstimates process, emphasizing simplicity and scalability.

Advice for #NoEstimates Adopters 

Luis recommends low-change experimentation with #NoEstimates to experience its benefits firsthand and stresses the importance of informative discussions over rigid planning.

Resource Recommendation 

For those considering #NoEstimates, Luis suggests starting with the "NoEstimates" book and following thought leaders like Vasco Duarte, Woody Zuill, and Allen Holub on social media.

About Luis Garcia

Luis is a Program Manager at Formula.Monks, specializes in developing impactful digital products. Luis has over 10 years of experience and several Agile certifications, he adeptly applies Agile frameworks to meet client needs. His background includes a Master's in Computer Engineering and an Executive MBA. He is also fluent in English, Spanish, and French, he values diverse work environments and continuous learning.

You can link with Luis Garcia on LinkedIn.

Lee Beckett: Using NoEstimates to Help Agile Teams Focus On Value, And Create Transparency - NoEstimates Unplugged Week

This is one of a series of episodes where Product Owners explain how they used, and benefited from #NoEstimates in their work with teams. 

To know more about #NoEstimates, sign-up to get the first 3 chapters of the book here.

Exploring #NoEstimates

Lee Beckett shares his journey from coder to Product Owner (PO), and how his diverse experience led him to question the effectiveness of traditional estimation techniques in agile environments. He discusses the adoption of a #NoEstimates approach, highlighting its benefits in simplifying processes and focusing on delivering value.

Lee illustrates how abandoning estimates, except for significant items, streamlined project workflows and improved team dynamics. This approach fostered a culture of trust and transparency, crucial for managing stakeholder expectations and focusing on product delivery.

Challenges and Solutions

Implementing #NoEstimates was surprisingly straightforward for Lee's team, emphasizing the importance of establishing trust and transparency with stakeholders from the outset.

Lee stresses honesty in forecasting and advises giving stakeholders meaningful insights rather than fixed dates to help manage expectations effectively.

After adopting #NoEstimates, the team's planning focused on work discussion rather than assigning numerical values, allowing for more flexible and goal-oriented sprint planning.

Measuring Success

Without traditional estimates, the team measures progress through product delivery and stakeholder feedback, ensuring a focus on value creation.

Lee advises teams to ensure open communication and clear prioritization with stakeholders before moving to #NoEstimates, ensuring a foundation for success.

Recommended Resource

For those interested in exploring #NoEstimates further, Lee recommends the "Agile for Humans" podcast, particularly the interview with Josh Anderson and Ryan Ripley.

About Lee Beckett

Lee Beckett, has over 17 years of experience in digital product development, and is a certified Product Owner and Lean Practitioner. Skilled in setting product goals and managing backlogs, Lee excels in guiding teams through the product lifecycle and fostering a culture of empiricism and learning in agile environments.

You can link with Lee Beckett on LinkedIn.

Viktor Didenchuk: Effective, Protective, Result-Oriented, The Traits of a Successful Scrum Product Owner

Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.

The Great Product Owner: Effective, Protective, Result-Oriented, The Traits of a Successful PO

When describing a great Product Owner and how they work, Viktor focuses first on effective communication; a great PO must clearly articulate what's working and what isn't to the team and stakeholders while fostering a reflective environment. Secondly, protection is essential; they must safeguard the team and product vision amidst constantly evolving technology, resisting the urge to chase every new trend. Finally, being result-oriented is vital; a great PO has a clear understanding of the desired outcomes and end state of the product. Viktor encapsulates this with the mantra, "It's always the leader who is wrong, and it's always the team who wins."

The Bad Product Owner: The Blind PO, Focusing On Short-Term Requests Instead Of The Overall Product Vision

Viktor discusses a common anti-pattern in product ownership: the 'blind PO' who lacks a clear vision. This type of PO is overly preoccupied with politics and managing stakeholder requests, neglecting the broader product vision. They often focus solely on satisfying immediate customer demands, which can work for some but not all scenarios. This approach can lead to team demotivation. Viktor emphasizes the need for POs to reflect, ask probing questions, and truly 'own' the product, considering long-term goals and the product's overall direction, rather than just short-term customer requests.

[IMAGE HERE] Are you having trouble helping the team work well with their Product Owner? We’ve put together a course to help you work on the collaboration team-product owner. You can find it at bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO’s collaborate.

About Viktor Didenchuk

Viktor began his career as a Software Engineer in the mid 2010's, before discovering a passion for coaching and facilitating value delivery. He currently serves as a Scrum Master at Lloyds Banking Group, the UK's largest retail bank, where he contributes to the Agile transformation of a 60,000+ employee organization, navigating and sharing the challenges encountered.

You can link with Viktor Didenchuk on LinkedIn. 

BONUS: The Future Of Agility, Experiment Driven Development, With Vasco Duarte

Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.

Merry Christmas, everyone! As we bid farewell to 2023, we present the final BONUS episode of this Christmas week—a glimpse into what we believe is the future for every Agile team out there. 

Brace yourselves for a deep dive into the heart of agility: learning at the speed of experimentation! Specifically, we'll explore the exciting realm of Experiment-driven development, a game-changer poised to reshape how teams approach learning and development. Don't forget, each episode this week complements the Coach Your Product Owner e-course, accessible at bit.ly/coachyourpo.

Throughout this week, we've delved into five crucial topics that every Scrum Master should master, with each topic complementing a module in the Coach Your PO e-course. Today's focus is on The spectrum of experimentation—a concept that promises to revolutionize the way teams learn and evolve.

The Spectrum of Experimentation

In previous episodes, we emphasized that writing and deploying software is the slowest and most expensive way to learn about what adds value to our product and business. Recognizing this, we introduced the idea of paper-prototype-based usability tests as a means to define and run experiments in 24 hours or less. However, this is just one facet of the vast landscape of experimentation.

Why does it matter? Not all experiments and hypotheses are created equal. While some ideas could lead to a 10x improvement in our product, others may offer incremental gains that are challenging to quantify. The key is to align the effort spent on validating hypotheses with their potential impact.

The Experiment Spectrum

Enter the experiment spectrum—a versatile range of experiments designed to collect information spanning from minutes to months. Let's explore some options based on time scales:

On the Hour Scale (Minutes):

• User Interviews: Direct conversations with potential users.

• Usability Tests: Quick assessments of user interaction.

• Paper Prototype Sales: A creative experiment—sell the paper version of the app to gauge interest.

On the Day or 24-Hour Scale:

• All of the Above: Intensify by including more interviews or tests.

• Customer Surveys: Quick insights if you have a means to reach your audience.

• Sales Calls with Existing Customers: Conduct a "sales pitch experiment" to validate core adoption/sales hypotheses.

On the Week or Month Scale:

• All of the Above: Scale up for more comprehensive data.

• Landing Page Tests: Experiment with different landing page variations.

• Email List Tests: Leverage existing mailing lists for experiments.

• Podcast Episodes and YouTube Videos: Engage with a wider audience.

• Running Software in Production: The traditional approach but still a valuable part of the spectrum.

The Value of the Spectrum

This spectrum acts as a strategic tool, ensuring teams don't over-invest in validating hypotheses that might not have a significant impact on their goals. Imagine how much unnecessary code could be avoided if teams could quickly validate assumptions!

Remember, an Agile principle is to "Maximize the work not done," and that the cheapest software to operate is the one that is not developed. Code is a liability, and confidence in its value must be established before investing in development, deployment, and maintenance.

Processes are Also a Domain of Experimentation!

As Scrum Masters, we are well aware that experimentation is not limited to products—it extends to our processes. Teams cannot improve unless they are constantly learning and experimenting. One powerful approach is self-experimentation, where teams start by experimenting with their process before venturing into product experiments. This builds confidence and familiarity with the concept of running experiments.

Experiment Driven Development: Summary

Today's episode focused on the evolution from learning to Experiment-driven development. Key takeaways include:

• Understanding the experiment spectrum—a range of experiments designed for different time scales.

• Examples of various experiment types, from quick-hour experiments to those spanning weeks.

• The importance of running experiments with processes before transitioning to product experiments.

All this week's episodes are companions to the Coach Your PO e-course, available at bit.ly/coachyourpo. Related modules include:

• Version 1, Module 4: Customer Needs – A valuable concept for assessing the potential impact of hypotheses.

• Version 1, Module 6: Quick Prioritization Techniques – Techniques applicable not just for backlogs but also for prioritizing assumptions and experiments.

• Version 2, Module 2: Setting up Product Goals – A crucial step before running experiments.

For more details or to purchase the Coach Your PO e-course, visit bit.ly/coachyourpo.

If personalized coaching is your preference, contact us at coaching@oikosofy.com.

As we conclude this special week of bonus episodes, we invite you to reach out for more information about our products and consulting services. Remember, a rising team lifts all products!

Wishing you all a Happy New Year! See you next week for another regular week of episodes.

About Vasco Duarte

Vasco is a leading voice in the agile community, known for his contributions to the development of agile methodologies and practices. He is the co-founder of Agile Finland and the host of Scrum Master Toolbox Podcast, the most popular Agile podcast in the world, which has more than 10 000 000 unique downloads. He is also the author of “NoEstimates: A novel look at how Agile can transform software development, making it both more sustainable, as well as incredibly profitable.” Vasco is a keynote speaker at many conferences and events, sharing his knowledge and experience with the agile community. With his passion and expertise in agile, Vasco has made a significant impact on the way software development is done today, helping organizations to become more efficient, flexible, and responsive to changing requirements.lYou You can link with Vasco Duarte on LinkedIn and connect with Vasco Duarte on Twitter.

BONUS: Unleashing Agile Experimentation, Accelerating Learning Cycles With 24h Experiments, With Vasco Duarte

Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.

Merry Christmas, everyone! In today's Christmas week BONUS episode, we're diving into the world of Agile experimentation, specifically exploring how to enable 24-hour experiments—a topic that promises to revolutionize the way we approach product development. As we explore this exciting subject, remember that each episode this week is a companion to the Coach Your Product Owner e-course, accessible at bit.ly/coachyourpo.

This week's episodes are designed to equip Scrum Masters with essential tools to assist their Product Owners in mastering five key areas. Today, we unravel the secrets of conducting rapid experiments that speed up your learning and development cycles.

First: Defining Experiments and Their Purpose in Product Development

Let's start by revisiting the Lean Startup methodology and its famed Build-Measure-Learn cycle. Lean Startup emphasizes that the purpose of "building" is not merely to deliver software but to validate hypotheses. Before running an experiment, it's crucial to define what you're trying to achieve, as discussed in Monday's episode on how to define value.

Taking Amazon’s website as an example, suppose a team aims to boost the conversion rate for users who have added items to their cart. The hypothesis could be: "Removing shipping costs from the checkout overview will result in a higher conversion rate for people who've added an item to their cart." This hypothesis, or belief, becomes the trigger for experimentation.

Second: Designing the Experiment

Once the hypothesis is clear, it's time to design the experiment. Think of it as crafting a story, but with a focus on experimentation. Here's a template to structure your experiment:

• Title: Increase Conversion Rate for People Who've Added an Item to the Cart by Removing Shipping Costs from the Checkout Overview.

• We Do: Specify the actions to set up the experiment.

• We Expect: Clearly state the anticipated outcomes.

• Data We Collect: List the crucial data points needed for analysis.

• Conclusion: Outline the lessons learned and set a date for analysis.

This structured template ensures clarity and sets the stage for a comprehensive understanding of the experiment.

Third: Designing 24-Hour Experiments

Before we start brainstorming stories and features that would need to be implemented by the development team, we should think about running experiments in 24 hours or less. We do this, because we want to avoid one of the major sources of waste in our processes: doing work that would not need to be done at all in the first place!

As we explore the experiment above, we define the key question as, "Would a person not shown shipping costs be more likely to complete a purchase after adding an item to the cart?"

To achieve faster learning, consider alternatives to software changes. In this episode, we explore some concrete alternatives to writing and deploying software when it comes to answer the key question defined above. 

One example we explore is: conducting usability tests using paper prototypes with a small group. Through qualitative analysis and user feedback, you can gain confidence in your hypothesis without investing time in extensive software modifications.

Running 24h Experiments: Summary

In summary, today's episode tackled critical aspects of designing and running experiments, emphasizing the importance of learning. Key takeaways include:

• Lean Startup's Build-Measure-Learn cycle focuses on validating hypotheses.

• Experiment design involves specifying actions, expected outcomes, data collection, and drawing conclusions.

• The concept of 24-hour experiments emphasizes the need for rapid learning.

All episodes this week complement the Coach Your PO e-course, available at bit.ly/coachyourpo. Related modules include:

• Version 2, Module 8: Critical Documents for the PO Role – Utilize Impact Mapping to identify assumptions and expectations for designing experiments.

• Version 2, Module 9: Collecting Feedback Faster – Explore methods for collecting feedback at various stages of product development, laying the groundwork for experiment-driven development.

• In Version 1, Module 3, we delve into Actionable Metrics—an indispensable tool for anyone looking to run successful experiments.

For more details or to purchase the Coach Your PO e-course, visit bit.ly/coachyourpo.

If personalized coaching is your preference, contact us at coaching@oikosofy.com.

Continue your journey of learning, keep supporting your team, and join us for the final episode tomorrow!

See you tomorrow!

About Vasco Duarte

Vasco is a leading voice in the agile community, known for his contributions to the development of agile methodologies and practices. He is the co-founder of Agile Finland and the host of Scrum Master Toolbox Podcast, the most popular Agile podcast in the world, which has more than 10 000 000 unique downloads. He is also the author of “NoEstimates: A novel look at how Agile can transform software development, making it both more sustainable, as well as incredibly profitable.” Vasco is a keynote speaker at many conferences and events, sharing his knowledge and experience with the agile community. With his passion and expertise in agile, Vasco has made a significant impact on the way software development is done today, helping organizations to become more efficient, flexible, and responsive to changing requirements.lYou You can link with Vasco Duarte on LinkedIn and connect with Vasco Duarte on Twitter.

BONUS: Helping Product Owners Make Decisions Quickly With Experiments, And Lean Startup, With Vasco Duarte

Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.

Merry Christmas, everyone! We hope your holiday season is filled with joy and festive cheer. As we continue our Christmas week BONUS episodes, today's focus is on empowering Product Owners (POs) to quickly make informed decisions based on the definition of value and value metrics. 

As usual in this year’s BONUS week of episodes, this episode is a crucial companion to the Coach Your Product Owner e-course, accessible at bit.ly/coachyourpo.

Quick Decision Making is the Goal!

While defining and measuring value are vital, our ultimate objective as Scrum Masters is to expedite the decision-making process. The pace of software development is directly correlated with the speed at which POs, stakeholders, and the team make decisions. Today, we discuss how Scrum Masters can help their teams, PO’s and stakeholders, make informed decisions faster.

Quick decision-making not only accelerates development but also contributes to learning faster, and discovering what does not need to be done at all! This aligns with Agile's principle of maximizing the work not done.

What Do POs Need to Make Decisions Quickly?

Understanding the obstacles to swift decision-making, we identify two types of obstacles:

1. Lack of Information: Relevant information is crucial for decision-making, and when it is missing it makes decisions slow, or impossible at all.

2. Timely Information: Having information at the right time ensures decisions align with current needs, information that is delivered too late does not help us avoid working on useless backlog items, among other things.

Let's delve into addressing each of these challenges.

First: Help Collect Information That Matters

1. Define Value: As discussed on Monday, defining the value for products is the first step in collecting the right information.

2. Measure Value: Tuesday's episode covered measuring value through metrics, providing valuable insights for decision-making.

3. Experimentation: Today, we discuss the process of experimentation to collect information efficiently. Real-world examples illustrate how experiments reveal the right metrics, emphasizing the importance of evaluating whether the collected information aids decision-making.

Second: Collect Relevant Information in a Timely Fashion

1. Strategic Metrics vs. Day-to-Day Metrics: As discussed in yesterday’s episode, distinguish between strategic metrics (top-level indicators) and day-to-day metrics (granular, changing metrics). These day-to-day metrics enable daily experiments and timely decision-making.

2. Metrics Tree: Introduced in yesterday’s episode, the Metrics Tree tool helps decompose top-level metrics into lower-level, day-to-day metrics. This tool facilitates running experiments that deliver the necessary information for informed decision-making.

Speeding Up Decision Making For Product Owners: Summary

In conclusion, today's episode highlighted the significance of quick and adaptive decision-making for the Product Owner role. The key takeaways include:

1. Ensure you're collecting the right information.

2. Collect that information swiftly, even within 24 hours (more on that in tomorrow’s episode).

All episodes this week are companions to the Coach Your PO e-course, available at bit.ly/coachyourpo. Today’s episode is a complement to the following modules:

• Version 1, Module 8: Defining the Perfect Sprint Goals – emphasizes using metrics for decision-making.

• Version 2, Module 02: How Scrum Masters Can Onboard a New or Beginner Product Owner – discusses goal setting and metrics.

• Version 2, Module 03: How to Work with a Skeptical PO – highlights the importance of requirements discovery in decision-making.

For more details, visit the Coach Your PO e-course page at: bit.ly/coachyourpo.

If live coaching aligns better with your needs, reach out to us at coaching@oikosofy.com.

Continue your learning journey, keep supporting your team, and join us for the next episode, where we discuss how to setup experiments that you can run in 24h or less!

About Vasco Duarte

Vasco is a leading voice in the agile community, known for his contributions to the development of agile methodologies and practices. He is the co-founder of Agile Finland and the host of Scrum Master Toolbox Podcast, the most popular Agile podcast in the world, which has more than 10 000 000 unique downloads. He is also the author of “NoEstimates: A novel look at how Agile can transform software development, making it both more sustainable, as well as incredibly profitable.” Vasco is a keynote speaker at many conferences and events, sharing his knowledge and experience with the agile community. With his passion and expertise in agile, Vasco has made a significant impact on the way software development is done today, helping organizations to become more efficient, flexible, and responsive to changing requirements.lYou You can link with Vasco Duarte on LinkedIn and connect with Vasco Duarte on Twitter.

Sofia Katsaouni: The Pitfalls of Multiple Product Owners For One Team, And A Solution That Worked

Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.

The Great Product Owner: Collaboration, Guidance And Trust, What Great PO’s work to achieve

In this episode, Sofia explores the qualities of a great Product Owner (POs), highlighting their guidance, collaborative problem-solving with the team, and how they shielded the team from interference. Trust-building is a key aspect, achieved by not imposing solutions and avoiding unilateral communication of deadlines. Sofia offers a tip on helping POs communicate "no" kindly to stakeholders. Additionally, she discusses the effective involvement of stakeholders, emphasizing onboarding and expectation-setting before demos.  

The Bad Product Owner: The Pitfalls of Multiple PO’s For One Team, And A Solution That Worked

In this episode, Sofia shares an early-career experience with dual Product Owners (POs) who were also team managers, causing chaos and confusion. She identifies the anti-pattern of having two POs without alignment, leading to an environment where the team felt constrained. Sofia provides tips on resolving this issue, advocating for a single PO, clarifying role responsibilities, and utilizing the PO proxy pattern to help coordinate and align stakeholder participation.

[IMAGE HERE] Are you having trouble helping the team work well with their Product Owner? We’ve put together a course to help you work on the collaboration team-product owner. You can find it at bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO’s collaborate.

About Sofia Katsaouni

Sofia is a dedicated Agile and Organizational Coach who places people and their needs at the forefront. Transitioning from electrical engineering, she applies analytical skills to empower high-performing teams. With an emphasis on trust and psychological safety, Sofia enables startups and scale-ups to foster human-centric, performance-driven cultures.

You can link with Sofia Katsaouni on LinkedIn. 

Thorben Pantring: A Stakeholder Engagement Revolution With A Review Bazaar, An Agile Change Story

Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.

Thorben discusses a change management challenge involving scheduling multiple sprint reviews for a scaling development effort. Attempting to consolidate reviews into one meeting resulted in decreased stakeholder participation and insufficient feedback. Consulting with Konstantin Ribel (who’s been a guest on the podcast), they conducted some experiments, seeking volunteers via internal Slack. Teams were named for specificity, and experiment learnings were documented, evolving into a company-wide change approach. Over time, the "science fair" of experiments expanded to larger audiences, employing demo environments instead of presentations. The result: a successful review bazaar with up to 100 stakeholders, a vast improvement from their initial few.

[IMAGE HERE] As Scrum Master we work with change continuously! Do you have your own change framework that provides the guidance, and queues you need when working with change? The Lean Change Management framework is a fully defined, lean-startup inspired change framework that can be used as the backbone of any change process! You can buy Lean Change Management the book at Amazon. Also available in French, Spanish, German and Portuguese.

About Thorben Pantring

Thorben is an experienced Scrum Master & Team Lead in the eCommerce space, showcasing expertise in leadership, LeSS, Scrum, team management, and engineering. With an insatiable desire for learning and a relentless pursuit of progress, Thorben embodies a fervent passion for leadership, agility, and technology.

You can link with Thorben Pantring on LinkedIn. 

Armin Mandara: When Product Owners Multiply, Making Decisions in a Maze of Stakeholders

Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.

The Great Product Owner: Empowering Teams, A Key PO Skill

Armin discusses the role of a great Product Owner (PO) in fostering team success. Drawing from an experience with a mixed team of internal and client-side members, he highlights the importance of clear communication and decision-making abilities in a client-driven setup. A standout PO, in his view, comprehends their role and limitations, excelling in making timely decisions and maintaining a pragmatic approach, even in challenging situations. They actively engage in discussions, emphasizing necessary trade-offs while demonstrating a keen awareness of the team's needs.

The Bad Product Owner: When POs Multiply, Making Decisions in a Maze of Stakeholders

Armin shares his experience in a B2B ecommerce setting, where a multitude of stakeholders complicated the Product Owner (PO) role. The presence of proxy POs, business analysts, and various other figures led to a lack of clear decision-making. Armin underscores the importance of collaboration between the PO and Scrum Master and emphasizes the need for transparency and timely decisions. He advises making issues transparent to stakeholders and offering suggestions for improvement to address this common anti-pattern. Clear ownership and decisive action are essential for effective product ownership.

[IMAGE HERE] Are you having trouble helping the team work well with their Product Owner? We’ve put together a course to help you work on the collaboration team-product owner. You can find it at bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO’s collaborate.

About Armin Mandara

Armin is the Head of Scrum Masters at IBM iX, a leading digital agency. With a career spanning seven years as a Scrum Master, Armin has partnered with numerous teams to successfully deliver top-notch digital products. His passion lies in enabling agile teams to achieve their goals and unleash their true potential.

You can link with Armin Mandara on LinkedIn.

Anna Mbengam: Rising From Disruption, After The Departure Of A Key Scrum Team Member

Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.

In this episode, Anna discusses a critical juncture at a startup where a key developer left, disrupting the team's dynamics. The team struggled to self-organize and lacked expertise after that senior developer left. Stakeholder expectations were high, making the situation even worse for the team. Anna implemented smaller group discussions, fostering a sense of ownership for specific development areas. This led to knowledge-sharing and a collaborative approach to improve performance. The team also sought stakeholder support in hiring. The episode highlights the importance of adaptability, stakeholder collaboration, and teamwork in agile development, especially in the face of unexpected departures.

[IMAGE HERE] Recovering from failure, or difficult moments is a critical skill for Scrum Masters. Not only because of us, but also because the teams, and stakeholders we work with will also face these moments! We need inspiring stories to help them, and ourselves! The Bungsu Story, is an inspiring story by Marcus Hammarberg which shows how a Coach can help organizations recover even from the most disastrous situations! Learn how Marcus helped The Bungsu, a hospital in Indonesia, recover from near-bankruptcy, twice! Using Lean and Agile methods to rebuild an organization and a team! An inspiring story you need to know about! Buy the book on Amazon: The Bungsu Story - How Lean and Kanban Saved a Small Hospital in Indonesia. Twice. and Can Help You Reshape Work in Your Company.

About Anna Mbengam

Anna, an accomplished Scrum Master and SAFe Coach since 2018, thrives in diverse industries like Personal Investments, Healthcare, Food & beverage, and Banking. She's authored 5 self-published guides aiding aspiring Scrum Masters, and her mentoring has transformed 200+ professionals into highly effective individuals for any organization.

You can link with Anna Mbengam on LinkedIn and read Anna’s books.

Lorraine Chambers: Using Experiments To Drive Agile Change, Lessons from a Test Automation Initiative

Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.

This story starts with an agile transformation featuring a shift-left initiative. The team faced challenges in implementing test automation due to unclear policies and time allocation. Recognizing the challenges faced by the teams, Lorraine engaged with managers and leaders, advocating to give teams the support they needed. Through that, it was possible to help the teams with guidance on Test-Driven Development and support in using an internal testing tool. When it comes to helping teams adopt new practices, Lorraine advises identifying policy and decision-makers, gathering relevant data, and proposing time-limited experiments for major changes, culminating in retrospective evaluations.

[IMAGE HERE] As Scrum Master we work with change continuously! Do you have your own change framework that provides the guidance, and queues you need when working with change? The Lean Change Management framework is a fully defined, lean-startup inspired change framework that can be used as the backbone of any change process! You can buy Lean Change Management the book at Amazon. Also available in French, Spanish, German and Portuguese.

About Lorraine Chambers

Lorraine's vision of excellence is summed up in the words of philosopher, Lao Tzu -- “A leader is best when people barely know he exists ... " She's held several roles in the Fintech industry, including Product Owner and Quality Assurance. She's a native New Yorker that loves travel, music and museums.

You can link with Lorraine Chambers on LinkedIn and connect with Lorraine Chambers on Instagram. 

Lorraine Chambers: Dismantling Silos, A Critical Aspect Of Helping Scrum Teams Succeed

Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.

In this episode, Lorraine explores the story of a midsized team within a larger organization. Operating in silos, the team members juggled disconnected tasks, leading to significant carryover between sprints, and an inability to fulfill sprint commitments. The silos led to limited collaboration which, in time, further hindered progress. Lorraine addressed concerns with the Product Owner and manager, but changes were deemed unfeasible at the time. This situation impeded the team's ability to self-organize. As reflection for Scrum Masters, Lorraine advises reflecting on the organizational team model and strategizing how to foster collective participation in sprint planning, shared goals, and self-organization within the team.

Featured Book of the Week: Radical Candor by Kim Scott

Lorraine discusses a pivotal book in her career: "Radical Candor" by Kim Scott, emphasizing its guidance on effective communication and feedback provision for coaches. The book advocates candidness in delivering both praise and criticism, underscoring the significance of nurturing relationships. Lorraine recounts an illustrative story from the book where a lack of candor led to performance issues. The lesson: timely, candid feedback is crucial.

[IMAGE HERE] Do you wish you had decades of experience? Learn from the Best Scrum Masters In The World, Today! The Tips from the Trenches - Scrum Master edition audiobook includes hours of audio interviews with SM’s that have decades of experience: from Mike Cohn to Linda Rising, Christopher Avery, and many more. Super-experienced Scrum Masters share their hard-earned lessons with you. Learn those today, make your teams awesome!  

About Lorraine Chambers

Lorraine's vision of excellence is summed up in the words of philosopher, Lao Tzu -- “A leader is best when people barely know he exists ... " She's held several roles in the Fintech industry, including Product Owner and Quality Assurance. She's a native New Yorker that loves travel, music and museums.

You can link with Lorraine Chambers on LinkedIn and connect with Lorraine Chambers on Instagram. 

Toby Rao: The Critical Impact of Effective Stakeholder Engagement in Agile Projects

Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.

In this episode, Toby shares his experience of working with a team in this transition. Toby emphasized the importance of addressing the initial challenges, including stakeholder engagement and logistics. He highlights the need to overcome mindset barriers within the organization. Key takeaways from this conversation include: the importance of seeking to understand before being understood, helping others grasp the team's needs, involving leads and stakeholders from other teams to identify blockers, and being open to negotiation for the team's success. Ultimately, creating shared understanding and transparency led to successful collaboration.

In this episode, we refer to the Tuckman Stages Of Group Development.

[IMAGE HERE] Recovering from failure, or difficult moments is a critical skill for Scrum Masters. Not only because of us, but also because the teams, and stakeholders we work with will also face these moments! We need inspiring stories to help them, and ourselves! The Bungsu Story, is an inspiring story by Marcus Hammarberg which shows how a Coach can help organizations recover even from the most disastrous situations! Learn how Marcus helped The Bungsu, a hospital in Indonesia, recover from near-bankruptcy, twice! Using Lean and Agile methods to rebuild an organization and a team! An inspiring story you need to know about! Buy the book on Amazon: The Bungsu Story - How Lean and Kanban Saved a Small Hospital in Indonesia. Twice. and Can Help You Reshape Work in Your Company.

About Toby Rao

Toby is an ICF-credentialed Coach and accredited IC Agile trainer, and practices as a certified Executive coach. With a dynamic Agile journey beginning in 2007, he's an active contributor to the global Agile community. He is based in Washington DC Metro, and speaks at Agile events worldwide and co-founded the A20 Agile conference. Toby also co-founded two thriving Agile meetups in the Washington DC area, with a combined 1300 members.

You can link with Toby Rao on LinkedIn and connect with Toby Rao on Twitter. 

Seye Kuyinu: Effective Agile Coaching, Building Contextual Understanding Beyond Scrum Guides

Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.

In this episode, Seye discusses a common anti-pattern that scrum masters can fall into, which involves not recognizing the distinction between Scrum practices and real-world situations. The organization Seye was working at had embraced Agile methodologies. However, Seye found some Agile adoption  issues like never ending meetings, one-hour daily standups, and conflicts during sprint planning. Seye suggests refraining from commanding the team and emphasizes the importance of not imposing the daily stand-up. He reflects on his own experience of lacking context and merely following the Scrum guide. To address this, we discuss forming coaching agreements with teams to ensure mutual understanding and effective implementation of Agile principles. Seye underscores the need for practical adaptation rather than rigid adherence.

In this episode, we also refer to Holacracy, and the book Getting Things Done by David Allen.

[IMAGE HERE] Recovering from failure, or difficult moments is a critical skill for Scrum Masters. Not only because of us, but also because the teams, and stakeholders we work with will also face these moments! We need inspiring stories to help them, and ourselves! The Bungsu Story, is an inspiring story by Marcus Hammarberg which shows how a Coach can help organizations recover even from the most disastrous situations! Learn how Marcus helped The Bungsu, a hospital in Indonesia, recover from near-bankruptcy, twice! Using Lean and Agile methods to rebuild an organization and a team! An inspiring story you need to know about! Buy the book on Amazon: The Bungsu Story - How Lean and Kanban Saved a Small Hospital in Indonesia. Twice. and Can Help You Reshape Work in Your Company.

About Seye Kuyinu

Seye has been a Scrum Master for about a decade now. He first connected to Agile, frustrated with the lack of adequate communication that plagues traditional complex projects. He finds People and Interactions over Processes & Tools cannot be overstated, while seeing that everything is a fractal- our individual, team, organization and societal challenges are the very same. The solution in every layer is the same- an understanding of ONENESS!

You can link with Seye Kuyinu on LinkedIn and connect with Seye Kuyinu on Twitter.

Khwezi Mputa: The Product Owner that knew how to collaborate with the Agile team

Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.

The Great Product Owner: The PO that knew how to collaborate with the team

In this segment, Khwezi highlights an exceptional Product Owner (PO) she collaborated with. The PO possessed a deep understanding of the product's market, customers, and business context, enabling her to continuously update the product effectively. She exhibited excellent teamwork despite the distributed nature of the team, showing awareness of diverse cultures. Her proficiency in user story mapping facilitated smoother processes, including onboarding new team members. Overall, the PO's comprehensive grasp of the product's ecosystem and her collaborative skills stood out as instrumental in driving the team's success.

The Bad Product Owner: The Unavailable and Bossy PO

While POs typically hold respected roles with authority over the product backlog, some misuse this status, behaving as if superior to the team. Often from management, such POs pose various challenges, including not being available often enough when the teams need their presence. Scrum Masters play a role in educating POs, advising team lift-offs to define roles, and coaching the POs to be active team participants. Khwezi emphasizes the Scrum Master's mediation role, and we discuss the “Coach Your PO e-course” which aims to help Scrum Masters have an effective PO collaboration. 

[IMAGE HERE] Are you having trouble helping the team work well with their Product Owner? We’ve put together a course to help you work on the collaboration team-product owner. You can find it at bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO’s collaborate.

About Khwezi Mputa

Khwezi is an experienced Agile coach, trainer, and IT professional since 2008. With diverse roles like Scrum Master, Agile Project Manager, and Business Analyst, she's active in the Agile community, promoting diversity. Passionate about teaching, she empowers individuals and organizations to reach their full potential through coaching and mentoring.

You can link with Khwezi Mputa on LinkedIn.

Khwezi Mputa: Visualizing Success And Coaching With Impact, With The Help Of A Coaching Backlog

Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.

In this episode, Khwezi emphasizes empowering teams over personal recognition. She highlights the importance of informing and involving stakeholders and sponsors, using a coaching backlog as a valuable tool. This backlog aids in feedback provision, achievement tracking, and maintaining focus. It also visually represents the team's journey. Khwezi acknowledges the challenge of conveying intangible scrum master efforts to sponsors and recommends visual tools like MURAL for clarity. Her insights encourage fostering empowerment and sharing impact beyond tangible metrics, reflecting her holistic approach to effective scrum mastering.

Featured Retrospective Format for the Week: The Movie Critic Retrospective

In the episode, Khwezi introduces “The Movie Critic” retrospective, a creative approach to retrospectives using movies. By asking the team to liken their experience to a movie genre, such as action or drama, they delve into struggles and reasons behind their choices. The question "do you recommend this movie?" prompts reflection. Utilizing tools like MURAL enhances the process, and Khwezi advises encouraging additional sharing to ensure comprehensive insights are captured. This cinematic retrospective technique offers an engaging way to explore team challenges and insights collaboratively.

[IMAGE HERE] Retrospectives, planning sessions, vision workshops, we are continuously helping teams learn about how to collaborate in practice! In this Actionable Agile Tools book, Jeff Campbell shares some of the tools he’s learned over a decade of coaching Agile Teams. The pragmatic coaching book you need, right now! Buy Actionable Agile Tools on Amazon, or directly from the author, and supercharge your facilitation toolbox! 

About Khwezi Mputa

Khwezi is an experienced Agile coach, trainer, and IT professional since 2008. With diverse roles like Scrum Master, Agile Project Manager, and Business Analyst, she's active in the Agile community, promoting diversity. Passionate about teaching, she empowers individuals and organizations to reach their full potential through coaching and mentoring.

You can link with Kwhezi Mputa on LinkedIn.

Khwezi Mputa: Breaking Down Dysfunctional Dynamics between a Scrum team and their Product Owner

Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.

In this episode, Khwezi discusses a challenging team scenario where great individuals struggled due to high-pressure dynamics and dysfunctional patterns. The Product Owner lacked decision-making authority, leading to delayed information and a proxy PO situation. This pressure caused scope creep and hindered technical debt management. Khwezi highlighted the importance of empowering the team to push back against excessive demands, coaching the PO to engage stakeholders effectively, and ensuring the right person fills the PO role. Addressing these issues was crucial for improving the product and fostering a healthier team dynamic.

If you need to support your Product Owner, we’ve created a course for you. You can access the Coach Your PO e-course here. 

Featured Book of the Week: Coaching Agile Teams by Lyssa Adkins

In this segment, Khwezi shares her recommended book, "Coaching Agile Teams" by Lyssa Adkins, which played a pivotal role in her self-improvement journey as a scrum master. This book provided valuable insights into guiding teams toward high performance. Khwezi emphasized using the Agile coaching competency framework and suggested self-assessment based on it. This framework led her to discover additional paths for growth. The book also highlighted the importance of exploring diverse topics to enhance skills. She mentioned the "Periodic Table of Scrum Master's Competencies" as a useful resource for understanding various skills enhancement facets.

[IMAGE HERE] Do you wish you had decades of experience? Learn from the Best Scrum Masters In The World, Today! The Tips from the Trenches - Scrum Master edition audiobook includes hours of audio interviews with SM’s that have decades of experience: from Mike Cohn to Linda Rising, Christopher Avery, and many more. Super-experienced Scrum Masters share their hard-earned lessons with you. Learn those today, make your teams awesome!  

About Khwezi Mputa

Khwezi is an experienced Agile coach, trainer, and IT professional since 2008. With diverse roles like Scrum Master, Agile Project Manager, and Business Analyst, she's active in the Agile community, promoting diversity. Passionate about teaching, she empowers individuals and organizations to reach their full potential through coaching and mentoring.