Scope creep (also called focus creep, requirement creep, feature creep, function creep) in project management refers to uncontrolled changes in a project's scope. This phenomenon can occur when the scope of a project is not properly defined, documented, or controlled. It is generally considered a negative occurrence that is to be avoided.

PropertyValue
dbpprop:abstract
  • Scope creep (also called focus creep, requirement creep, feature creep, function creep) in project management refers to uncontrolled changes in a project's scope. This phenomenon can occur when the scope of a project is not properly defined, documented, or controlled. It is generally considered a negative occurrence that is to be avoided. Typically, the scope increase consists of either new products or new features of already approved product designs, without corresponding increases in resources, schedule, or budget. As a result, the project team risks drifting away from its original purpose and scope into unplanned additions. As the scope of a project grows, more tasks must be completed within the budget and schedule originally designed for a smaller set of tasks. Thus, scope creep can result in a project team overrunning its original budget and schedule. If the budget and schedule are increased along with the scope, the change is usually considered an acceptable addition to the project, and the term “scope creep” is not used. Scope creep can be a result of: disingenuous customer with a determined value for free policy poor change control lack of proper initial identification of what is required to bring about the project objectives weak project manager or executive sponsor poor communication between parties Agile software development based on subjective quantifications. Scope creep is a risk in most projects. Most megaprojects fall victim to scope creep. Scope creep often results in cost overrun. A value for free strategy is difficult to counteract and remains a difficult challenge for even the most experienced project managers.
  • Enfilament d'abast (també anomenat enfilament de requeriments, enfilament de funcions) en gestió de gestió de projectes fa referència a canvis incontrolats en l'abast del projecte. Aquest fenomen pot ocórrer quan l'abast d'un projecte no està adequadament definit, documentat o controlat. Es considerat generalment un fet negatiu a evitar. Típicament, l'increment de l'abast consisteix en nous productes o noves funcions per a dissenys de productes ja aprovats, sense els corresponents increments en recursos, calendari o pressupost. Com a resultat, l'equip del projecte corre el risc de sortir-se del seu propòsit original i dedicar-se a afegiments no planificats. A mesura que l'abast d'un projecte creix, més tasques han d'ésser completades dintre del pressupost i el calendari originalment dissenyats per a un conjunt més petit de tasques. D'aquesta forma, l'enfilament d'abast pot tenir com a resultat que l'equip de projecte excedeixi el seu pressupost i calendari originals. Si el pressupost o el calendari són incrementats juntament amb l'abast, el canvi es normalment considerat com un afegiment acceptable al projecte, i el terme 'enfilament d'abast' no s'utilitza. L'enfilament d'abast pot ser resultat de: Control de canvis pobre Falta d'identificació inicial adequada de què s'ha de portar a terme sobre els objectius del projecte Gestor de projectes dèbil Comunicació pobre entre parts L'enfilament d'abast és un risc en molts projectes. Molts megaprojectes cauen víctimes de l'enfilament d'abast.
dbpprop:hasPhotoCollection
dbpprop:otheruses4Property
  • Telescopic sight Mounting_issuestelescopic sight
  • project management
  • dbpedia:Firearms
dbpprop:reference
dbpprop:wikiPageUsesTemplate
rdfs:comment
  • Scope creep (also called focus creep, requirement creep, feature creep, function creep) in project management refers to uncontrolled changes in a project's scope. This phenomenon can occur when the scope of a project is not properly defined, documented, or controlled. It is generally considered a negative occurrence that is to be avoided.
  • Enfilament d'abast (també anomenat enfilament de requeriments, enfilament de funcions) en gestió de gestió de projectes fa referència a canvis incontrolats en l'abast del projecte. Aquest fenomen pot ocórrer quan l'abast d'un projecte no està adequadament definit, documentat o controlat. Es considerat generalment un fet negatiu a evitar.
rdfs:label
  • Scope creep
  • Enfilament d'abast
owl:sameAs
skos:subject
foaf:page
is dbpprop:redirect of