Time-Planning in Software Projects29 Mar 2016
The following information is quoted from the classic software project book The Mythical Man-Month. According to its author, Fred Brooks, the total available time for a “serious” software project should be divided roughly in:
- 1/3 of the time for planning
- 1/6 of the time for coding
- 1/4 of the time for component testing
- 1/4 of the time for system testing
Well, the dedication of only 1/6 of the time for the actual programming sounds very little, but every developer can verify that the work never ends after the coding phase. If you want to deliver high quality, bug-free software, a substantial amount of time needs to be reserved for the testing afterwards. This is especially true if your software project is about a component of a bigger software system.
On the other hand, a well executed planning phase reduces the needed time for the programming significantly. The planning phase is the most important one, because it impacts all the following steps.