Thursday, December 2, 2010

How too much project management slows down projects

At first look, managing risks by splitting the project into milestones, and assigning full features for each milestone, should help projects. But, as I've seen so far, it puts all the developers to work on the same part of the program, having merge conflicts, especially if each code piece needs to wait for code review, in the meantime gathering more conflicts.

Another slowdown comes from the fact that the code for each feature needs to be understood by more developers (because both DeveloperA and DeveloperB work on Feature1 in Milestone1, and both work on Feature2 in Milestone2), and understanding code and specs takes up a good amount of time.

Perhaps the classic waterfall model is not that bad after all, and we'll see a return of it in 5-10 years.

No comments:

Post a Comment