Scope Creep

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

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 ?
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.
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.
Keywords: Acquisition Reform, Cost Growth, Requirements Stability, Requirements Creep, F/A-18 Hornet
Satellite programs have their own special kind of requirements creep, though.
Over the course of 60 years, DoD has attempted to improve its acquisition and life cycle process through a series of incremental changes to address requirements creep, cost growth, funding instability, and technical risk.
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.
It is commonly recognized that requirements creep is a primary source of cost and schedule growth experienced by most major defense acquisition programs.
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.
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.
Traditionally, if you look at the DAPA [Defense Acquisition Performance Assessment Project] Report, the QDR [Quadrennial Defense Review], the CSIS [Center for Strategic and International Studies] Report, the Defense Science Board reports, you learn that big drivers in terms of cost growth and schedule delays are the fact that technology has to come into the mainstream prematurely and that requirements creep has escalated in inordinate ways.

Full browser ?