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.
Farlex Financial Dictionary. © 2012 Farlex, Inc. All Rights Reserved
Mentioned in ?
References in periodicals archive ?
Moreover, aside from mission, it is the rapid pace of technology that drives requirements creep. (21) So if holding the line on requirements may limit cost growth, it will also diminish the technology advantage that ships take to sea.
Bartosik and Lee credit Richards with keeping the team focused and providing top cover against requirements creep and other issues.
Streamlining was accomplished with a process designed to eliminate "requirements creep"--the Achilles' heel of all IT projects--and what has sometimes been called the "sandbox effect." The TCA project was managed by requiring that all features and changes be approved by the Rapid Application Development (RAD) team.
The previous attempt, known as VH-71, was led by Lockheed Martin and AgustaWestland --now Leonardo--and was canceled by then-Defense Secretary Robert Gates in 2009 for cost overruns and requirements creep, according to analysts.
The program managers decry "requirements creep" while the requirements managers--representing the warfighter--wonder what went wrong with their clear, specific and necessary operational requirements.
Keywords: Acquisition Reform, Cost Growth, Requirements Stability, Requirements Creep, F/A-18 Hornet
So far, the program has been free of requirements creep, he said.
As the Defense Acquisition University (DAU) develops and teaches classes, faculty members hear much about "'Big R' Requirements" versus "'little r' requirements" and volumes about "requirements creep." The challenge is how to turn desirements into requirements.
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.
* Requirements Growth--A current trend toward "late binding" along with the revision of customer requirements during development risks an introduction of an unintended requirements creep. This disrupts predevelopment cost and schedule estimates.
The tradeoff for tixed-price contracts was that the services had to freeze their requirements in place, thus preventing the so-called "requirements creep," that had military customers adding new features to a program while it was under development, therefore boosting its costs, and sending the program over budget.
Paul Jacobs attributed the problem of "requirements creep" to the shifting of support bases over time and the comparatively short position tenures of high-level military decision-makers.

Full browser ?