This article discusses the drop in productivity and decline in reliability and how to fix these issues.
This article discusses functional design and how this second phase of software development must reduce divergences to the levels that business practice can tolerate.
This article discusses how SLIM can be used to prepare for and assess the costs the year 2000 may bring.
“The only way to increase product quality and reduce cost while concurrently improving product development speed is to fundamentally change the development process itself.”
Christopher Meyer 1
“That phrase, time boxing, has a fine manly ring to it,” the vice president said, grinning broadly. “I like it.”
“What does it mean to you,” we inquired.
“First you box in the development time you allow a project to have,” he answered.
“No more shilly-shallying around. You draw a box on the time line, like this (Figure 1). The project people know they have to deliver at the end of the box.”
Hidden Rule #1: “We can’t make sensible business decisions with such wide unknowns,” upper managers say.
From Tom DeMarco, Why Does Software Cost So Much?, Dorset House Publishing, 1995, 237 pages.
What is the minimum of control that will maintain the process? Peter F. Drucker 1