The Product Owner and Scrum Master Brain Transplant! Mwuhahahaha!!!

Imagine you are a Mad Agile Scientist and have a diabolical experiment to conduct - what would happen if you exchanged the brains of a Product Owner and Scrum Master? Mwuhahahaha!!! How would the body of a Product Owner with the brain of a Scrum Master act? And vice versa?

Perhaps the Scrum Master would now treat the team like a backlog? This Scrum Master would be focused on value and maintaining a coaching backlog of team and person improvements. This Scrum Master is refining the team, crafting a group that delivers value.

And perhaps the Product Owner might treat the backlog like a team? Rather than backlog refining, they coach the backlog. They would be focused on nurturing, protecting, and empowering the backlog. The backlog might transform from an irritation into a labor of love.

Although this experiment sounds terrible, this change of perspective might be what you need to reanimate your dead team or backlog.

Join the fun and come learn what horrifying results await!


Outline/Structure of the Talk

2' - Mad Agile Scientist introduction

18 ' - Treat the backlog like a SM

  • Backlog coaching instead of backlog refining
  • Nurture
  • Protect
  • Remove impediments
  • Experiment
  • Conflict resolution
  • Happy

18 ' - Treat the team like a PO

  • Team refining instead of team coaching
  • Backlog of individual and team improvements
  • Create and prioritize stories
  • Determine value and AC
  • Have a global DoD
  • Demonstrate
  • Improvement feedback loop

2' - Conclusion

Remainder of total timebox (45') - Q&A, approx 5'


  • The Product Owner can immediately apply soft skills to humanize their backlog
  • The Scrum Master can immediately apply the concept of growing people and teams via a backlog

Presentation History:

Presentation history of this session:

XP 2018 Porto

Alex's conference and presentation history:

  • Agile Open Northwest 2012 - Session Leader
  • Übermind ÜnConference 2012 - Session Leader
  • MobileUXCamp Seattle 2012 - Session Leader
  • Seattle Kaizen Camp 2012 - Session Leader
  • MAQCon 2012 - Cofounder
  • MobileUXCamp Seattle 2013 - Session Leader
  • Seattle Kaizen Camp 2013 - Session Leader
  • MobileUXCamp Seattle 2014 - Session Leader
  • Seattle Kaizen Camp 2014 - Session Leader
  • Construx Software Executive Summit 2014 - Facilitator
  • Shell Developers Summit 2015 - Keynote Speaker
  • Scrum Coaching Retreat Seattle 2015 - Volunteer Team
  • Un:Conference Canberra 2016 - Session Leader
  • Agile2016 - Volunteer Team
  • UX Australia 2016 - Speaker, Reviewer
  • Agile Coach Camp Sydney 2016 - Session Leader
  • Agile Tour Sydney 2016 - Facilitator
  • StartCon 2016 - Pitch Competitor
  • Global Scrum Gathering San Diego 2017 - Reviewer
  • Global Scrum Gathering Singapore 2017 - Speaker (Rating = 4.5/5)
  • Agile Coach Camp Sydney 2017 - Session Leader
  • Scrum Gathering India 2017 - Speaker, Facilitator, Coaches' Clinic
  • Lean Agile Systems Thinking Canberra 2017 - Organizer, Speaker (Rating = 5/5)
  • Lean Agile Systems Thinking Melbourne 2017 - Speaker (Rating = 5/5), Facilitator (Rating = 4.4/5)
  • Lean Agile Systems Thinking Sydney 2017 - Speaker
  • Scrum Gathering Melbourne 2017 - Speaker (Rating = 2nd highest session at conference), Coaches' Clinic
  • AgileNZ 2017- Speaker
  • Scrum Gathering South Africa 2017 - Speaker
  • Business and Enterprise Agility Conference India 2017 - Speaker
  • Business Agility Conference NYC 2018 - Facilitator
  • 1st Conference Melbourne 2018 - Facilitator
  • XP 2018 Portugal - Facilitator, Speaker
  • Scrum Gathering Rio 2018 - Speaker
  • Agile2018 San Diego - Speaker

Speaking References:


Learning Outcome

  • Product Owners will learn that they should love their backlogs. This shift in attitude and how they view their work can transform their tedious backlog maintenance into a labor of love. For example, a PO may change the meeting title from "Backlog Refining" to "Backlog Coaching".
  • Scrum Masters will learn that it's OK to push the team to grow. This change in perspective will empower the Scrum Master to focus on value and encouraging the best they can get from their team. For example, a Scrum Master may deploy backlogs targeted to improving skills of team members.
  • All attendees will be introduced to the concept that traditional role paradigms can be shifted.

Target Audience

Scrum Masters, Product Owners, Agile Coaches

Prerequisites for Attendees




schedule Submitted 2 years ago

  • Alex Sloley
    Alex Sloley
    Alex Sloley
    schedule 2 years ago
    Sold Out!
    50 Mins
    Hands on Session

    The Business Model Canvas and the A3 Report are classic examples of using visualization tools to help you/a team/an org analyze and plan. However, you might find that available canvases don't really suit your needs. Would you really use the traditional Business Model Canvas for a legacy product in a large enterprise?

    Come learn about classic examples of canvases and what they are trying to achieve. Learn about a simple framework that enables you to build a custom canvas that is suited to your needs. And walk away with a custom canvas, because you are going to build your own canvas in this workshop!

  • Alex Sloley

    Alex Sloley - Liberating Structures... 36 tried and true facilitation techniques to amp up your org's collaboration

    Alex Sloley
    Alex Sloley
    Alex Sloley
    schedule 2 years ago
    Sold Out!
    50 Mins
    Hands on Session

    The communication tools of Liberating Structures will teach you how to facilitate the discussions your org needs. I am going to demonstrate how to use these techniques in the workshop. And all the attendees are going to be fully immersed and ready to wield their new knowledge the very next day at work.

    Come learn how to help your team(s), org(s), and company(ies)!!!

    For more information, watch my video at

    A version of this workshop that was presented at Agile Tour Sydney 2016 is at

  • Gabor Devenyi

    Gabor Devenyi / Alex Sloley - The magic number is 10

    25 Mins

    Why are Agile teams supposed to be small? How big are they supposed to be? Most agilists tend to agree that a team of ten people works well.

    But what is it about the number 10 that makes it the “magic” number?

    Since the start of human evolution, people formed groups to be more effective. Whether it was the hunt for a mammoth or going to war, working in teams ensured a greater chance of success.

    There have been various researches from Dunbar’s paper through the Scrum Guide to military formations about the ideal number of people in a team.

    We’ll discuss the historical, scientific and cultural reasons why 10 seems to be the magic number of forming effective teams.

    Does the number of team members really matter? Is 10 really the magic number. You will get an answer that will help you to create effective teams with the right amount of people.