Scaled Retro’s: going against the rulebook

I feel like this isn’t my story to tell. I work with an amazing set of talented individuals in a start-up that literally started with 1 employee. 18 months in, we sit at approximately 150 team members across the group, and 100 within my brand alone. As we scale, so incredibly rapidly, we need to make sure we constantly review ourselves. Not just the business of best ways to make money, but also the best ways to keep our team, our processes and our culture alive and churning like a well-oiled machine. So, being an agile organisation, embodying what we teach our clients every day, we run our own ceremonies. The challenge we face is that as we grow, we need to make sure each individual has a voice and has opportunity to have that voice heard. This session is all about scaling retros for large groups, a real life approach to what we’ve done, what’s worked and what has.. not worked so well... from there we’re going to put our money where our mouth is and run a scaled retro on the LAST conference.


Outline/Structure of the Interactive

  • Our organisation

The structure, the design and the layout, it matters because it actually in a lot of ways reflects any organisations which are large, have acquisitions, smaller parts and larger parts, imbalances, poor communication in areas.

  • Our retros
  • Retro 1: the classic retro 20 people
  • Retro 2 & 3: 50 people
    • Situation problem: time limitations our solution time boxing
    • Retro actions from the previous retro
    • eNPS and gathering people’s mood on the night
  • Retro 4: 70 people
    • Situation problem: did an engagement survey, analysis paralysis
    • Non actionable actions
    • Interfered with org strategy
  • Retro 5: Next up. 100 people
    • Have we learnt from our mistakes?
    • Took the potential topics from mgt
    • Polled it with the team to select the top ones for the night
    • Timeboxing and only providing 1 action each
    • Framework of what that action needs to be limited to

We continually adapt as we grow,

  • Comparison of what we do to Less & Safe

Where we fail/they fail

Where we succeed/they succeed

  • Scaled retro of LAST

Learning Outcome

how to scale a retro for large groups

Target Audience

Business analysts, scrum masters

schedule Submitted 1 year ago

Public Feedback

    • Cathy Jamshidi

      Cathy Jamshidi - User adoption: selling the story to developers

      Cathy Jamshidi
      Cathy Jamshidi
      Sr. Business Analyst
      schedule 1 year ago
      Sold Out!
      30 Mins

      User adoption is one of the most challenging things about projects. When they are consumer facing applications, you can measure your success through the number of click throughs, time spent by users reading pages or product purchases, money they spend. Consumers want to use your product because it fulfils a need or a want. Conversely, when a product or service is required out of obligation, regulation or to maintain a standard, and it doesn’t necessarily fit a need or a problem they’re trying to solve, then consumers don’t want to use the goods or services.

      Welcome to the world of application security. Application security is sexy in theory, hacking at systems, breaking in, being a rebel without a cause, but what happens when you try and roll application security tooling out to hundreds of developers where many of them have less than no interest in embedding another tool into their software delivery lifecycle? How do you keep it sexy, interesting, engaging and make them want to use it?

      This is the story of how we rolled out appsec tooling to developers, our wins, our failures, and the rollercoaster journey we went through. The aim is to provide some insight into how different behaviours influence user adoption and hopefully some takeaways you can use when you're involved in such projects, either as part of a delivery team or conversely as an end user

    • Ronnie-Lee Freeburn

      Ronnie-Lee Freeburn / Malvika Nath - Scrum For Business

      30 Mins

      There is a common misconception that Agile, Scrum and Kanban are just buzz words used by IT.

      So what happens when the entire organisation commences driving forward with SAFe and other Agile at scale frameworks, of course the the business wants to jump on the Agile train too.

      Recently at a large energy provider employing the SAFe methodology we were granted the opportunity to create one of the first business scrum teams.

      In this presentation we will reflect on the journey of the business becoming Agile, which challenged the ways of thinking for everyone involved.

      Topics to be covered include:

      • Who are the members of a Business Scrum Team
      • What existing business role can work as a Product Owner
      • How to breakdown business gant charts and processes into story cards
      • Facilitating a Business Focused PIP
      • How does a Business PO Sync work and who should attend
      • How to work with external agencies that are intergeral to the scrum team
    • Oliver Deacon

      Oliver Deacon - Sit down, don't stand up - one path to improved focus and collaboration

      Oliver Deacon
      Oliver Deacon
      Scrum Master
      Liberty Financial
      schedule 1 year ago
      Sold Out!
      30 Mins

      Have you ever spent time in a stand up that just doesn’t seem to meet the ‘short and to the point’ objective? As the stand up limps into a second hour it seems more like a ceremony to celebrate endurance than a chance to check-in, connect and calibrate.

      Your mind wanders, you shuffle awkwardly from foot to foot, you fade in and out of caring and context and wonder if there is a better way, one which saves on shoe leather and stamina.

      We wondered the same.

      This talk will elaborate on how we experimented with asynchronous stand-ups and through inspection and adaption opened an avenue to awesome collaboration.