This article was originally published in The Critical Path email newsletter, March 21, 2003.
Not all products are the same. Not all development teams are the same. Why then do companies try to create standardized development processes? Logically, any company attempting this does so to alleviate perceived problems with recurring errors, things like rework, slow cycle times and information defects. The theory is that a formulaic approach will drive down process variability with benefits similar to how a standard tooling process will drive down defects and scrap in manufacturing. Unfortunately, this is not without its costs. Continue reading