A NOTE ON WASTE MANAGEMENT IN SOFTWARE ENGINEERING (INTERNATIONAL FOCUS)
N. K. Srinath · IJITR International Journal of Innovative Technology and Research - IJITR International Journal of Innovative Technology and Research · 2013
U.S. government and businesses spent approximately $81 billion on canceled software projects, and another $59 billion for budget overruns. Their survey claimed that in the United States, only about one-sixth of all projects were completed on time and within budget, nearly one third of a projects were canceled outright, and well over half were considered "challenged." Of the challenged or canceled projects, the average project was 189 percent over budget, 222 percent behind schedule, and contained only 61 percent of the originally specified features.[1] One reason for the varied conclusions is that most failed projects are never studied—even by the organization that experienced the failure. A failure is defined as any software project with severe cost or schedule overruns, quality problems, or that suffers outright cancellation. Some of the important points that are to be considered to avoid waste in software Engineering are discussed in this paper.