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.

BONUS: Helping the PO Measure Value, Unwrapping Metrics Mastery 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, dear listeners! We hope your festive season is filled with joy and warmth. Today marks another special BONUS episode in our Christmas week lineup, and we're diving into the crucial topic of helping Product Owners measure value. If you missed our previous episode on defining business value, be sure to check it out as today's content builds upon those insights.

This episode, like all others this week, is a companion to the Coach Your Product Owner e-course, accessible at bit.ly/coachyourpo.

Why We Need To Help Product Owners Measure Value

Ever envisioned driving a familiar road blindfolded? Many teams find themselves in a similar predicament, knowing their backlog and delivery process well but lacking clarity on their goal. A backlog of items, as emphasized yesterday, is not a goal.

Defining Value is Not Enough; We Must Measure It

While some teams may define goals, many stumble when it comes to measuring them early and consistently. Aligning with the Agile Manifesto, this episode emphasizes why continuous delivery of valuable software needs to be complemented with the same continuous measurement of value!

Leading and Lagging Indicators and Why That's Important

In this episode, we discuss the distinction between leading and lagging indicators. Leading indicators provide insights into future events, while lagging indicators validate that the product is delivering value. Explore the significance of both in making informed decisions.

The Difference Between Strategic Metrics and Day-to-Day Metrics (The Metrics Tree Technique)

Building on yesterday's discussion about understanding the company's strategy, we explore the transition from strategic metrics (lagging indicators like revenue) to day-to-day metrics. This transition is essential for ensuring daily value delivery and supporting short-term, customer-focused experiments.

In this segment, we discuss the Metrics Tree technique which Vasco learned from Chris Matts.

Product Dashboards for the PO and the Team

Product Dashboards emerge as a crucial tool to keep teams focused on the right metrics throughout the development process. These dashboards visualize product goals, the target customer, current and future sprint goals, and key metrics. They serve as a cornerstone for team accountability, fostering self-management and autonomy.

In this episode, we discuss a Product Dashboard similar to the one illustrated below: 

How To Measure Value: A Summary

In today’s episode, we covered the following steps to help the PO measure value:

1. Define value (discussed in the previous episode).

2. Define appropriate metrics for the defined value.

3. Consider both leading and lagging indicators.

4. Ensure a balance of strategic and day-to-day metrics for decision-making.

5. Build a product dashboard with the PO and the team to enhance self-accountability and self-management.

Explore these concepts further in the Coach Your PO e-course:

• Module 3 (Version 1.0): Setting up ACTIONABLE metrics, distinguishing between ACTIONABLE and Vanity Metrics.

• Module 2.0: Scaling up the Product Owner role for multiple teams and products, featuring insights into Product Dashboards and Vision.

• Module 09: Techniques for quick feedback and leveraging process metrics critical for the discussed product dashboard.

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

If personalized coaching suits your needs, reach out to us at coaching@oikosofy.com.

Keep learning, keep helping your team, and we'll catch you in the next episode!

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: How To Help Your Product Owner Define Value, 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! This is the first of 5 BONUS episodes for this Christmas week, each of these episodes complements one or more modules of the Coach Your Product Owner e-course available at bit.ly/coachyourpo.

In this episode, we delve into one of the crucial aspects of the Product Owner role: defining, measuring, and leveraging Business Value. 

Why We Need To Help Product Owners Define Value

We start the episode with an anecdote about training Product Owners. Many of those POs faced the common challenge of delivering from a well-defined, high-pressure backlog, which led them and their teams to "be a slave to the backlog."

Those PO’s understood during the training, that having a crystal clear definition of value turned the decision-making process into a more straightforward one.

The Importance Of Strategy In Defining Value

Not every company has a crystal-clear strategy. And having a clear strategy is critical to be able to have conversations about what value means for a specific organization. In this episode, we also talk about how we can help PO’s facilitate conversations with key stakeholders to align the product with the company's success metrics.

Translate the Product's Strategic Goal into a Concrete Measurable Goal

Eventually, once the strategy for the organization, and the product are clear, we need to turn the company's strategy into tangible, measurable goals for the product. In this episode, we walk through an example, we learn about Luke, the Scrum Master, assisting Leya, the ambitious PO, in reducing call center wait times through strategic experiments.

Key Steps:

1. Understand Company Strategy

2. Link Product to Strategy and Goals

3. Define Specific, Measurable Metrics

This Episode Is A Companion To The Following Coach Your PO E-Course Modules

This episode is a companion, and a complement to the following Coach Your PO e-course modules:

• Module 2 (Version 2.0): Onboarding New Product Owners

• Module 8: Critical Documents and Artifacts for Product Owners (featuring impact mapping)

• Module 3 (Version 1.0): Metrics That Drive Product Success

To learn more about the e-course, and to purchase it, visit bit.ly/coachyourpo.

If you think that getting coaching is a better option yourself, you can contact us at coaching@oikosofy.com

Keep learning, keep helping your team, and have a wonderful Christmas!

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.

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.

In the previous episode (here: https://youtu.be/T1doj980NuE) we explored the things that need to be in-place before a great Product Roadmap can be built. In this episode, we use those concepts to create a Mission, Vision, Strategies, and Goals for our organization and product, the Arguing Agile Podcast!

#productmanagement #agile #career 

0:00 Topic: Crafting a Mission, Vision, & Strategy
1:13 The Existing Mission/Vision
2:20 Crafting the Vision
4:08 Going One Step Deeper
5:56 The Original Mission
7:09 Working on the Mission
9:26 Roman Pichler's Product Vision Board
10:22 Assumption-Based Vision/Mission
11:39 Forming a Coherent Mission
13:30 Completing Mission
16:06 Kernel of a Good Strategy
18:19 Sidebar: Strategy in the Real-World
20:09 How This All Fits
21:22 Strategy #1
22:23 Saying No
23:50 Continuing Strategies and Separating Goals
27:19 Identifying Redundant & Missing Strategies
29:18 Now, the Roadmap
31:08 We Probably Should Have Cut This Section
31:29 Wrap-up
32:43 Another (Unnecessary) Wrap-Up
----------------------
Watch us on YouTube: 
https://youtu.be/RFXd3rqzprA

Subscribe to the Arguing Agile Podcast: https://www.youtube.com/@arguingagile/featured

Or listen on: 
Apple Podcasts:
https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596

Google Podcasts:https://podcasts.google.com/feed/aHR0cHM6Ly9mZWVkcy5idXp6c3Byb3V0LmNvbS8xNzgxMzE5LnJzcw

Spotify:
https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3

Amazon Music:
https://music.amazon.com/podcasts/ee3506fc-38f2-46d1-a301-79681c55ed82/Agile-Podcast

Stitcher:
https://www.stitcher.com/show/agile-podcast-2
----------------------
AA104 - Creating a Mission, Vision, & Strategy