Scaling an engineering team

The team grows, delivery doesn’t

The development team has grown, and it ships no more features per sprint than before. Every new hire brings meetings and waiting before bringing capacity, because everyone changes the same code at once, parts of the system have no team answerable for them and the processes are those of a smaller group.

Book a call

Does this sound familiar?

  • We’ve hired, and yet we ship the same number of features per sprint as before, or fewer.
  • Pull requests stay open for days, waiting for a review or for a merge without conflicts.
  • A growing share of the week goes on meetings to align with others.
  • Senior people spend more time coaching and answering questions than developing.
  • Habits that worked when we were few, like deciding on the fly or everyone integrating on the same branch, now create queues.

Where does the coordination that slows the team come from?

Coordination that grows faster than the team shows in meetings, in reviews that wait, in merges. Code without boundaries is the cause that weighs most, because it brings confusion about responsibilities with it.

  1. Coordination grows faster than the team

    Fred Brooks observed back in the 1970s that adding people to a late project makes it later, because communication channels grow faster than people. If everyone’s work depends on that of many others, every new arrival brings more meetings and more waiting.

  2. Everyone works on the same code

    In coupled code with no clear internal boundaries, more people end up modifying the same modules, so merge conflicts, regressions and the time spent working out what a change will touch all grow. The parallel work you expected from hiring stays on paper, because the code doesn’t allow it.

  3. Modules that belong to everyone

    When a module has no team answerable for it, every decision needs the opinion of several people and reviews stall waiting for whoever knows that part. With a team responsible for each area, decisions move back close to the people doing the work.

  4. Processes designed for a smaller team

    A single branch everyone integrates on, a slow pipeline, a shared test environment: with a few developers these were small frictions, with many they become queues. The path by which work reaches production needs rethinking as the team grows.

What changes when the team grows without slowing down

New people work in parallel with the ones already there, on separate parts of the code, and become useful quickly because they find readable boundaries and someone who points to the parts to work on first. The time spent coordinating stays proportionate to the work, even as the team keeps growing.

In planning, the team discusses the roadmap knowing how much work it can sustain, and a new hire picks up where the work stands today.

How has your team grown?

Pull requests left open and recurring meetings show where the team loses capacity as it grows. We look at them together to see where coordination weighs most.

We use your data to respond to your request. Read our Privacy Policy.