Advisor

Don’t Assume a 30% Allocation for Testing on Software Budgets

Posted February 25, 2016 | Technology |

In the days of large waterfall projects, organizations made the assumption that a software budget was allocated one-third per major category: analysis and design, develop, test. This was the rule of thumb that was used to generate a high-level estimate (HLE). This rule of thumb was great when it was applied evenly to all three categories. However, what usually happened on software projects is that the first two categories needed more time and it inevitably came at the expense of testing in an effort to stay on budget.

About The Author
Maurizio Mancini
Maurizio Mancini is leader in the quality and process industries with a sixth sense for Agile, quality, and business process. He is best known for cutting through the noise and getting to the heart of any organizational problem whether that problem consists of choosing the right software development process, implementing modern quality approaches, adapting project/product/portfolio management to fully leverage Agile, or just finding the right… Read More
Don’t have a login? Make one! It’s free and gives you access to all Cutter research.