Project Creep

Project Creep

A slang term for the gradual extension of a deadline, especially if the parameters of a project are moved repeatedly. See also: Scope creep.
References in periodicals archive ?
At this step in the process, you have reached a logical point in the project plan path that including features outside of the chosen path could be allowed with little issues, and could be argued that it is not project creep.
To begin, organizations should right-size projects and provide appropriate executive oversight to avoid project creep.
For example: project creep won't just hurt you, now it can kill you because it's not just your time at stake.
Project creep occurs when the project grows to become something never intended or approved.
To avoid project creep, where the scope of the project begins to change after the plan, it's important to agree upfront on which variables are flexible and which are non-negotiable.
For the purposes of this article the term project creep will refer to the adding of projects and processes to the workload without prior establishment of clear linkages as to how these activities align with the organizational strategic objectives.
As such they are often adopted and become project creep.
Project creep is the cancer that usually causes a project to miss overall goals and increases management frustration.
To protect against project creep (that dangerous lack of adherence to project parameters, goals, and agreements), Flagstar set a date after which no further additions could be made to the scope of the design and implementation.
There is also a danger of project creep, with users being able to directly ask developers to build functionality that was never within the original project scope.
Letting the scope of the project creep much beyond the initial boundaries on which budgets and timelines were predicated risks harming one or more of the legs of the iron triangle: quality, speed, and cost.
Full browser ?