• Language

  • Copyright © 2012 for code art and programming by Developers Global, New York City, USA, all rights reserved, ® 2008 - 2012
  • open panel

How to cheat Brook’s Law with Agile Software Development

Many Agile Software Development aficionados know for a fact that adding additional manpower to hasten a project in its late stages usually backfires and has the exact opposite effect.

During the 70’s, Fred Brooks proved this and also coined a law stating that adding more personnel to a software project that’s on its last lap but it’s running late only delays it even further. This is true most of the time when it comes to mobile and desktop application development or any other software development services.

However, this doesn’t mean that there aren’t ways to work around it using the power of Agile Software Development. After all, even Fred Brooks himself admitted that his law is oversimplified so it’s only logical that there must be some ways to outsmart it. Well, we are glad to say that our software developers did just that with amazing results and because we are good guys we want to share it all with you.

Below are the 5 Developers Global golden rules to outwitting Brook’s law by adding more manpower to your software development project.

1. Keep team dependencies to a strict minimum.

This one is pretty easy to understand. The more independent your teams are, the faster they will get things done. A lot of time can be wasted on negotiating and clearing stuff up, especially when you add more people in the mix. This is why splitting tasks intelligently and with minimum dependencies is vital.

2. Ensure a compact working environment.

This is another thing that should stand to reason but surprisingly, many project managers overlook it. When members of different teams are able to ask questions and receive answers by simply raising their heads or looking over their shoulders, things get done much faster. This is also a good way to keep other team members constantly updated on the ebb and flow of the process.

3. Set daily meetings.

This one is pretty much self-explanatory. Gather your teams for at least 15 minutes every day and talk strictly about cross-team issues.

4. Make sure you have an Agile codebase.

If you don’t have an agile code base to begin with, you can pretty much forget about delivering the project on time. At Developers Global we always strive to keep our code as “learnable” as possible and this sure comes in handy when we have to push the limits of a project. New teams will assimilate information much faster and will be able to quickly jump into the fray.

5. Avoid leaving features only partially finished.

This is another thing that can really mess up your plans for delivering the goods on time. If there are too many aspects to your project that are only partially completed, new team members will have too much of a hard time grasping all the assorted information coming their way.

If you are struggling with a project’s deadline, go over this list first. If it all checks out then it is all up to you to deliver on time. Feel free to leave us a line describing your Agile experiences.