Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Outpace '25, Ensemble Working: The ultimate in ...

Avatar for Clare Sudbery Clare Sudbery
October 15, 2025
1

Outpace '25, Ensemble Working: The ultimate in collaboration

These are the slides that were delivered at Outpace Conf in Manchester, on Thurs 16th Oct 2025.

Clare dives deep into Ensemble Working (aka “mob programming”). When teams work well together, this can have a considerable impact on the quality of the software they deliver. But how can we help this to happen? Clare examines the benefits in detail, explains how she teaches the technique to new teams, and describes why it is her approach of choice in many different situations.

Avatar for Clare Sudbery

Clare Sudbery

October 15, 2025
Tweet

Transcript

  1. @ClareSudbery Software Teaming All the brilliant minds working together on

    the same thing, at the same time, in the same space, and at the same computer. Woody Zuill
  2. @ClareSudbery Wrong assumptions about software development • Software development is

    a reducible activity • Software development is primarily about coding Daniel Terhorst-North
  3. @ClareSudbery Software development is not a reducible activity Daniel Terhorst-North

    “It is a fallacy that software development is reducible, like building a wall, where you can measure who lays the most bricks, or whose work is the neatest or needs the fewest corrections.”
  4. @ClareSudbery The worst programmer I know “The reason that Tim

    [Mackinnon]’s productivity score was zero, was that he never signed up for any stories. Instead he would spend his day pairing with different teammates.” Daniel Terhorst-North
  5. @ClareSudbery Making developers productive “Your highest-value developers are 10x by

    enabling other developers! Often the least useful thing they can be doing is producing code themselves.” Daniel Terhorst-North
  6. @ClareSudbery Wrong assumptions about software development • Software development is

    a reducible activity • Software development is primarily about coding Daniel Terhorst-North
  7. @ClareSudbery Most of programming is… • learning the business domain

    • understanding the problem • assessing possible solutions • validating assumptions through feedback and experimentation • ensuring consistency at scale Daniel Terhorst-North
  8. @ClareSudbery Measures become targets “Measuring leads to behavior change –

    behaviour change including coming up with creative ways to improve those measurement scores even at the expense of results that everyone agrees matter.” Kent Beck and Gergely Orosz
  9. @ClareSudbery Goodhart’s Law “When a measure becomes a target, it

    ceases to be a good measure.” Kent Beck and Gergely Orosz
  10. @ClareSudbery Ensemble work maximises learning • Onboarding new team members

    • Starting a new project • Learning together as a team • Engagement and job satisfaction
  11. @ClareSudbery Ensemble work maximises collaboration • Good collaboration => increased

    quality • Obliterates context switching • Minimises bottlenecks • Getting the best out of everyone...
  12. • We treat everyone with kindness, consideration and respect All

    roles are enhanced by a working agreement "Creative Commons Share-alike license with attribution Emily Bache, ProAgile" @ClareSudbery
  13. Ensemble Roles • Facilitator • Typist • Navigator • Supporter

    • Rotate all except facilitator often Typist Navigator Facilitator Supporters "Creative Commons Share-alike license with attribution Emily Bache, ProAgile" @ClareSudbery
  14. Typist role • Enters code into the computer • Expert

    use of IDE, shortcuts, code navigation, searching • Listens to the team Typist Navigator Facilitator Supporters "Creative Commons Share-alike license with attribution Emily Bache, ProAgile" @ClareSudbery
  15. Navigator role • Leads the work • Makes decisions •

    Communicates clearly about direction and intent • Explains details if needed Typist Navigator Facilitator Supporters "Creative Commons Share-alike license with attribution Emily Bache, ProAgile" @ClareSudbery
  16. Supporter role • Help the navigator (when they ask) •

    Raise concerns (at the right time) • Ask questions so you understand what’s going on Typist Navigator Facilitator Supporters "Creative Commons Share-alike license with attribution Emily Bache, ProAgile" @ClareSudbery
  17. Facilitator role • Provides meta-guidance • Moderates dysfunction • Highlights

    excellence • Can be part time • Aims to become redundant Typist Navigator Facilitator Supporters "Creative Commons Share-alike license with attribution Emily Bache, ProAgile" @ClareSudbery
  18. @ClareSudbery Summary – Part 1 • Start small – try

    it out! • You don’t need permission if you’re getting results • Focus on team metrics • Pay attention to long term quality – bugs and tech debt • Use the opportunity to remove unnecessary ceremonies • Regular retros
  19. @ClareSudbery Summary – Part 2 • Make your own rules

    – change as you go • Start with a strong structure • Keep people engaged • Agree on rules of engagement and keep reviewing • Let people opt out • Pay attention to enablers and blockers • Get help!
  20. @ClareSudbery “In order to be successful in modern development organizations,

    software developers need new skills. These skills are not easily learnt on a short training course or at a university. Practices like Continuous Integration and Test-Driven Development require developers to change their minute-by- minute habits and ways of working.” Emily Bache Samman Technical Coaching Society