Retrospectives are one of the most effective continuous improvement practices, but how do you scale them beyond your team? This is the problem I faced with running regular retrospectives with more than 50 people. And with many large organisations scaling agile or adopting the likes of SAFe we are going to run into this problem much more frequently. After all we must not forget that agile is underpinned by the ethos of reflection and improvement.

During this talk, I will discuss how companies like Spotify & Atlassian have implemented scaled retrospectives, and where their stories have helped us and what didn’t work for us. I will share some practical tips on how we’ve run awesome scaled retrospectives and avoid wasting everyone’s time. Learn how you too can improvement your entire organisation, not just your development teams.

2 favorite thumb_down thumb_up 2 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist

Outline/structure of the Session


  • What is everyone else doing? Learn about all the different ways to run scaled Retrospectives


      • We’ll cover how different frameworks and companies are running scaled retrospectives:
        • SAFe
        • LeSS
        • Spotify
        • Atlassian


  • Practical tips to run awesome scaled retrospectives


      • Sharing detailed practical tips (i.e. preparation, multiple facilitators) to ensure scaled retrospectives run smoothly, are effective, and deliver on the promise of continuous improvement


  • Sharing my story


    • I’ll provide stories of how I am running scaled retrospectives on my current program
    • What have we learnt along the way, what did we try, what did we improve

Learning Outcome

This talk will cover the following learning objectives:

  • Learn about the benefits of running a scaled retrospective across programs
  • Gain an understanding of how different frameworks and companies have adopted scaled retrospectives
  • Gather a number of practical tips on how to run effective scaled retrospectives
  • Hear about stories on how scaled retrospectives have been run in real life - what worked, what didn’t work

Target Audience

Scrum Masters, Retrospective facilitators, Agile Coaches

schedule Submitted 1 year ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Michael Chik
    By Michael Chik  ~  1 year ago
    reply Reply

    Hi Ryan,

    Thanks for your submission! You mention that you will cover how different frameworks and companies run retrospectives and I wanted to check if you have first-hand experience in them (SAFe, LeSS, working at Spotify or using their model, working at Atlassian).



    • Ryan McKergow
      By Ryan McKergow  ~  1 year ago
      reply Reply

      Hi Michael,

      My apologies for the belated reply. I got caught up presenting at 1st Conference (Melbourne) last week. 

      To answer your question, I have limited experience with the frameworks/companies mentioned and plan to cover it from more a theoretical perspective. I only want to cover this quickly (i.e. 5 minutes) and spend the majority of my time on my practical experience. The intent of doing it this way is to do a comparison between what the frameworks say is done, and what other companies do, and then tie it back to my real world experience. Sharing the tips that I have learnt and specific examples from the program level retrospective I have been facilitating. 


      I hope this helps.




  • Teng Daniel
    Teng Daniel
    schedule 1 year ago
    Sold Out!
    60 Mins

    We are going to share a case study of how we kick start a LeSS (Large Scaled Scrum) agile transition in FDA (Food & Drugs Administration) regulated organization. The product is a surgery X-Ray machine and the team include software engineer, mechanical engineer, electronical engineer. After one year journey, the product get shipped within one year comparing to 2.5 years of previous version. No bug was found after shipping the product so far and the build time reduced from 20+ hrs to 2.8 secs. What made these happen? One of the biggest challenges is how to enable cross-functional and self-managing team and to make it more challenging, everyone had to choose their role and teams. In this talk, I am going to share with you how we official launched the change and how we as agile coaches support in their agile journey. 




  • Liked Marcio Sete

    Marcio Sete - The Ten Principles of the DevOps Movement

    Marcio Sete
    Marcio Sete
    Agile Coach
    schedule 1 year ago
    Sold Out!
    60 Mins

    It looks like that DevOps has hit the Mainstream. Gartner says by 2016, DevOps will evolve from a niche to a mainstream strategy employed by 25 percent of the Global 2000 Organizations.

    This means that the DevOps Movement has already begun to be treated as a mainstream market, with vendors enjoying a toolset market that reached US$2.3 billion in 2015. Besides that, a whole ecosystem has been created in order to surf the DevOps wave. Certifications, events, communities, portals, media companies, marketing speeches, roles, self-promotions and more among others.

    This talk is about the 10 Principles of the DevOps Movement. I will attempt to strip DevOps back to its bare essentials and explain the core principles of this great movement, which is definitely changing the digital business game around the World.


    Here are the principles of the DevOps movement, covered in this session:

    1. DevOps is a Journey. You will never get there. It never ends...

    2. DevOps is not just about tooling and automation. You’ll need far more to achieve business high-performance and people’s happiness

    3. Achieve a state of flow! The secret is doing small and frequent changes.

    4. As a Team, everybody should be working on the same process, technologies and script languages.

    5. There is just one lifecycle, the business one.

    6. If the business is not involved, believe me, you are not doing DevOps!

    7. Focus on a strategic Business Applications and improve continuously.

    8. Create your own unicorn!

    9. Do whatever needs to be done to help the business win!

    10. Share the results. Help people believe they can also help change the world!
  • Liked Hugo Messer

    Hugo Messer - Why distributed teams don't work and what to do about it

    Hugo Messer
    Hugo Messer
    schedule 1 year ago
    Sold Out!
    45 Mins

    Based on 10 years distributed agile experience, Hugo's distilled 5 core problems in distributed software development. To find solutions, he's gathered data from hundreds of practitioners and wrote 6 books about remote teams. In this workshop, participants will learn practical solutions to make distributed teams work better. 

  • Naresh Jain
    Naresh Jain
    schedule 2 years ago
    Sold Out!
    45 Mins

    As more and more companies are moving to the Cloud, they want their latest, greatest software features to be available to their users as quickly as they are built. However there are several issues blocking them from moving ahead.

    One key issue is the massive amount of time it takes for someone to certify that the new feature is indeed working as expected and also to assure that the rest of the features will continuing to work. In spite of this long waiting cycle, we still cannot assure that our software will not have any issues. In fact, many times our assumptions about the user's needs or behavior might itself be wrong. But this long testing cycle only helps us validate that our assumptions works as assumed.

    How can we break out of this rut & get thin slices of our features in front of our users to validate our assumptions early?

    Most software organizations today suffer from what I call, the "Inverted Testing Pyramid" problem. They spend maximum time and effort manually checking software. Some invest in automation, but mostly building slow, complex, fragile end-to-end GUI test. Very little effort is spent on building a solid foundation of unit & acceptance tests.

    This over-investment in end-to-end tests is a slippery slope. Once you start on this path, you end up investing even more time & effort on testing which gives you diminishing returns.

    In this session Naresh Jain will explain the key misconceptions that has lead to the inverted testing pyramid approach being massively adopted, main drawbacks of this approach and how to turn your organization around to get the right testing pyramid.

  • Liked Ryan McKergow

    Ryan McKergow - The art of facilitating great collaborative workshops

    45 Mins

    We can no longer afford to work independently of our customers. In order for teams to deliver great outcomes to them, we need to collaborate with them. Agile encourages collaboration via many different workshops instead of treating requirements as a constract. But, running these workshops can be hard. In order to ensure we don’t waste time, we need a strong facilitator.

    In this talk, I want to share with you some of the tips and techniques that I have learnt over the years when it comes to running great collaborative workshops. We will go through some of the key Agile workshops: Project Inceptions, 3 Amigos sessions, Story Kick-offs, Retrospectives and more. You too can learn the art to facilitating great collaborative workshops.