• Skip to main content
  • Skip to after header navigation
  • Skip to site footer

Shaping Software

Enduring Ideas in the Realm of Software

  • About
  • Topics
  • Best Software Books
  • Archives
  • JD Meier.com

Adding People to Late Projects Makes Them Later

Aug 4, 2008 by JD

Adding people to late projects makes them later.  This can be counter-intuitive.  In Requirements-Led Project Management: Discovering David’s Slingshot, by Suzanne Robertson and James Robertson explain how adding people to late projects makes them later.

The Least Knowledgeable People Prevent the Most Knowledgeable People from Working
According to Suzanne and James, adding people to a late project, makes the project later:

The problem of adding people means disrupting the rhythm that your existing team has established.  It increases the number of communication paths. New people penalize the existing team.  When new members arrive, they almost certainly have to ask questions.  And the most obvious people to ask are the most skilled – and therefore the most valuable to you –people on the team.  So you end up with the least knowledgeable people preventing the most knowledgeable people from working.

Key Take Aways
I’ve lead many projects over the years, and I have found that adding people to late projects does make them later. Here’s my key take aways:

  • Adding people can disrupt the rhythm.
  • Adding people increases the number of communication paths.
  • Adding people can slow down the existing team.
  • The least knowledgeable people prevent the most knowledgeable people from working.
Category: Project-ManagementTag: Project-Management, Schedule, Teamwork

About JD

Previous Post:Visual Threats and Countermeasures
Next Post:Architectural Patterns vs. System Metaphorsarchitectural pattern vs metaphor

Reader Interactions

Comments

  1. Alik | PracticeThis.com

    Aug 4, 2008 at 8:11 am

    Sometimes adding people and making projects later is done on purpose in order to milk some more budgets. Sad but true… like you once called out – context precision. What’s your context?

  2. JD

    Aug 6, 2008 at 2:53 am

    Hey Alik

    Well — that reaffirms it works, right 😉

  3. John Ahrens

    Aug 7, 2008 at 2:27 am

    Of course, Fred Brooks said the same thing in the Mythical Man-Month, in about 1978! We may observe the rules, but we never learn them.

  4. JD

    Aug 7, 2008 at 3:38 pm

    Hey John –

    I wonder if Web 2.0 back then would have helped capture/share the timeless lessons?

    It’s funny how much of the great knowledge is spread over “threads and heads” and “time and space” and treasure-troves of timeless book nuggets.

Trackbacks

  1. Make a List of the Jobs to Be Done | Project Management | Patterns and Practices for Software Engineering. says:
    Sep 28, 2008 at 1:46 am

    […] Adding People to Late Projects Makes Them Later […]

Sidebar

Recent Posts

  • What is ChatGPT?
  • Agile Performance Engineering
  • What is Cybersecurity?
  • Software Security Threats: A Comprehensive Guide
  • What is Software Security?

Popular Posts

Best Software Books of All Time
Best Practices for Project Management
Best Practices for Software Development
Customer-Connected Engineering
How To Frame Problems Better
How To Pitch Business Ideas Better
How To Structure Vision Scope Presentations
Intro to Lean Software Development
Lean Principles for Software Development
The Enterprise of the Future