Scope Creep

(redirected from Requirements creep)
Also found in: Encyclopedia.

Scope Creep

A slang term for the gradual extension of the goal or parameters of a project, especially if they are changed by a manager attempting to make himself/herself look good to his/her own managers.
Mentioned in ?
References in periodicals archive ?
The VXX program, which was canceled in 2009, was plagued by delays and requirements creep, said Richard Aboulafia, vice president of analysis at the Teal Group, a Fairfax, Virginia-based defense and aerospace market analysis firm.
To do so the Navy must, as we have seen, limit increases in personnel costs, prioritize shipbuilding budgets and stabilize construction rates, limit increases in operations and maintenance costs, reduce research and development funding, and prevent requirements creep and cost growth.
Arguably, analysis never is finished because requirements managers must keep refining those requirements to respond to changes in threats, to apply lessons learned during system development, and to prevent requirements creep.
Keywords: Acquisition Reform, Cost Growth, Requirements Stability, Requirements Creep, F/A-18 Hornet
These initiatives represented a comprehensive list of measures with the potential to lower costs, but did not address the major causes of cost growth in weapon systems such as technical risk, requirements creep, and cost-plus business arrangements (Foelber, 1982).
Satellite programs have their own special kind of requirements creep, though.
Capability, requirements, and affordability areas this JCDPR effort addressed include: requirements creep, improving capability metrics, prioritizing capabilities, promoting joint solutions that properly balance cost, schedule, and performance, improving affordability integration in the requirements development process, and developing incremental performance parameters and metrics.
The lack of schedule focus creates a culture that has historically called for a total system solution despite notorious requirements creep and a never-ending component to sub system-to-system test.
It is commonly recognized that requirements creep is a primary source of cost and schedule growth experienced by most major defense acquisition programs.
Situation Awareness, Requirements Creep, and the Central Problem
Program managers can use this forum to control requirements creep and seek moderation of requirements, which become costly drivers in the system design.
For instance, unless tightly controlled, OM may exacerbate the enduring problem of requirements creep that plagues programs today.

Full browser ?