Many software projects collapse under the weight of their own complexity. During the collapse, these projects go through familiar stages as they die a painful death.
- First come minor schedule slips
- Then a missed milestone
- Then an adjustment to the master schedule extending the end-date a bit
- Then 80-hour weeks for the programmers
- Then the altered schedule does not work either
- Then management looses touch with reality and insists all is fine
- The end-date comes and goes with no working software.
- And then the finger pointing begins to assess blame.
Why does this happen again and again, to competent organizations that are able to complete other types of projects efficiently? The problem is that many of the world’s large software projects are just too darn complicated.
This article introduces the 1-5-10 Rule for software design to help your projects avoid a similar fate.
Full article here….
http://www.chc-3.com/pub/1-5-10_rule.pdf
Chuck