171:
34:
281:
Properly defining project scope requires thorough investigation by the project manager during the initial planning phase of a project. Failure to gather all information from all relevant stakeholders is a common reason for incomplete scope statements and missing requirements, which can frequently and
272:
Ineffective project management communication between a client and the project manager is a leading effect of project scope creep. An assignment that is not understood correctly will turn out to be completely different from clients vision. With that being said clients can also be to blame as they may
282:
easily lead to scope creep later in the project. It is essential that everyone on the team understands the project requirements thoroughly -- and that the project sponsor and relevant stakeholders have signed off on those requirements -- before execution of the project begins.
153:, generally experienced after the project begins. This can occur when the scope of a project is not properly defined, documented, or controlled. It is generally considered harmful. It is related to but distinct from
306:
Another huge cause of scope creep is the communication gap between the stakeholders. Clients may not respond quickly enough to the project managers causing the project to run into a bottleneck.
298:
Sometimes project teams tend to start adding additional features in order to impress the client. This may not work and tend to cause more work for such project and throw off the scope.
502:
290:
Adoptions and adhering to project management practices and project management processes are confirmed methods of preventing scope creep from dismantling the project.
590:
550:
327:. A "value for free" strategy is difficult to counteract and remains a difficult challenge for even the most experienced project managers.
309:
These aspects can affect the operational efficiencies of companies, especially when involved in long-term relationships. Scope creep is a
573:
476:
451:
492:
235:
98:
207:
70:
422:
254:
117:
525:
214:
77:
591:"The need to improve communication about scope changes: frustration as an indicator of operational inefficiencies"
192:
55:
221:
84:
188:
51:
645:
203:
66:
347:
150:
357:
22:
181:
44:
414:
407:
373:
439:
319:
18:
Continuous or uncontrolled growth in a project's scope, at any point after the project begins
497:
379:
8:
228:
157:, because feature creep refers to features, and scope creep refers to the whole project.
91:
444:
Identifying and
Managing Project Risk: Essential Tools for Failure-Proofing Your Project
621:
142:
625:
613:
569:
544:
472:
447:
418:
362:
605:
589:
Invernizzi, Diletta
Colette; Locatelli, Giorgio; Brookes, Naomi J. (July 4, 2018).
609:
384:
352:
639:
617:
367:
154:
342:
337:
324:
314:
195: in this section. Unsourced material may be challenged and removed.
301:
21:
This article is about project management. For the firearms term, see
170:
33:
146:
310:
588:
285:
276:
293:
58:. Unsourced material may be challenged and removed.
406:
302:The communication gap between project stakeholders
526:"What is Scope Creep and How Can You Control It?"
637:
267:
549:: CS1 maint: multiple names: authors list (
493:"Managing Scope Creep in Project Management"
398:
440:"Chapter 3. Identifying Project Scope Risk"
431:
273:not see a clear vision of what they want.
145:is continuous or uncontrolled growth in a
255:Learn how and when to remove this message
118:Learn how and when to remove this message
563:
466:
446:(3rd ed.). AMACOM. pp. 50–52.
437:
23:Telescopic sight § Mounting issues
638:
404:
523:
413:(Second ed.). AMACOM. pp.
286:Lack of project management practices
193:adding citations to reliable sources
164:
56:adding citations to reliable sources
27:
277:Failure to capture all requirements
13:
505:from the original on July 11, 2014
409:Fundamentals of Project Management
14:
657:
598:Production Planning & Control
323:). Scope creep often results in
317:fall victim to scope creep (see
294:Addition of unnecessary features
169:
160:
32:
180:needs additional citations for
43:needs additional citations for
582:
557:
517:
485:
460:
1:
610:10.1080/09537287.2018.1461949
530:All Things Project Management
391:
268:Poorly defined project scope
7:
330:
10:
662:
568:(Third ed.). Apress.
471:(Third ed.). Apress.
348:Scope (project management)
20:
524:Guerrero, Felicia, PMP.
358:Escalation of commitment
564:Sanghera, Paul (2019).
467:Sanghera, Paul (2019).
313:in most projects. Most
438:Kendrick, Tom (2015).
374:The Mythical Man-Month
501:. February 22, 2023.
405:Lewis, James (2002).
320:Megaprojects and Risk
139:kitchen sink syndrome
498:Villanova University
380:Second-system effect
189:improve this article
52:improve this article
646:Project management
143:project management
575:978-1-4842-3910-0
478:978-1-4842-3910-0
453:978-0-8144-3609-7
363:Instruction creep
265:
264:
257:
239:
135:requirement creep
128:
127:
120:
102:
653:
630:
629:
595:
586:
580:
579:
561:
555:
554:
548:
540:
538:
536:
521:
515:
514:
512:
510:
489:
483:
482:
464:
458:
457:
435:
429:
428:
412:
402:
260:
253:
249:
246:
240:
238:
197:
173:
165:
123:
116:
112:
109:
103:
101:
60:
36:
28:
661:
660:
656:
655:
654:
652:
651:
650:
636:
635:
634:
633:
593:
587:
583:
576:
562:
558:
542:
541:
534:
532:
522:
518:
508:
506:
491:
490:
486:
479:
465:
461:
454:
436:
432:
425:
403:
399:
394:
389:
333:
304:
296:
288:
279:
270:
261:
250:
244:
241:
198:
196:
186:
174:
163:
124:
113:
107:
104:
61:
59:
49:
37:
26:
19:
12:
11:
5:
659:
649:
648:
632:
631:
604:(9): 729–742.
581:
574:
556:
516:
484:
477:
459:
452:
430:
423:
396:
395:
393:
390:
388:
387:
385:Software bloat
382:
377:
370:
365:
360:
355:
353:Planning poker
350:
345:
340:
334:
332:
329:
303:
300:
295:
292:
287:
284:
278:
275:
269:
266:
263:
262:
177:
175:
168:
162:
159:
126:
125:
40:
38:
31:
17:
9:
6:
4:
3:
2:
658:
647:
644:
643:
641:
627:
623:
619:
615:
611:
607:
603:
599:
592:
585:
577:
571:
567:
560:
552:
546:
531:
527:
520:
504:
500:
499:
494:
488:
480:
474:
470:
463:
455:
449:
445:
441:
434:
426:
424:0-8144-7132-3
420:
416:
411:
410:
401:
397:
386:
383:
381:
378:
376:
375:
371:
369:
368:Mission creep
366:
364:
361:
359:
356:
354:
351:
349:
346:
344:
341:
339:
336:
335:
328:
326:
322:
321:
316:
312:
307:
299:
291:
283:
274:
259:
256:
248:
237:
234:
230:
227:
223:
220:
216:
213:
209:
206: –
205:
204:"Scope creep"
201:
200:Find sources:
194:
190:
184:
183:
178:This section
176:
172:
167:
166:
161:Common causes
158:
156:
155:feature creep
152:
148:
144:
140:
136:
133:(also called
132:
122:
119:
111:
100:
97:
93:
90:
86:
83:
79:
76:
72:
69: –
68:
67:"Scope creep"
64:
63:Find sources:
57:
53:
47:
46:
41:This article
39:
35:
30:
29:
24:
16:
601:
597:
584:
566:PMP in Depth
565:
559:
533:. Retrieved
529:
519:
507:. Retrieved
496:
487:
469:PMP in Depth
468:
462:
443:
433:
408:
400:
372:
343:Cost overrun
338:Anti-pattern
325:cost overrun
318:
315:megaprojects
308:
305:
297:
289:
280:
271:
251:
245:January 2022
242:
232:
225:
218:
211:
199:
187:Please help
182:verification
179:
138:
134:
130:
129:
114:
108:January 2022
105:
95:
88:
81:
74:
62:
50:Please help
45:verification
42:
15:
535:October 14,
131:Scope creep
392:References
215:newspapers
78:newspapers
626:116129580
618:0953-7287
640:Category
545:cite web
509:June 16,
503:Archived
331:See also
229:scholar
147:project
92:scholar
624:
616:
572:
475:
450:
421:
415:29, 63
231:
224:
217:
210:
202:
94:
87:
80:
73:
65:
622:S2CID
594:(PDF)
236:JSTOR
222:books
151:scope
141:) in
137:, or
99:JSTOR
85:books
614:ISSN
570:ISBN
551:link
537:2022
511:2023
473:ISBN
448:ISBN
419:ISBN
311:risk
208:news
71:news
606:doi
191:by
149:'s
54:by
642::
620:.
612:.
602:29
600:.
596:.
547:}}
543:{{
528:.
495:.
442:.
417:.
628:.
608::
578:.
553:)
539:.
513:.
481:.
456:.
427:.
258:)
252:(
247:)
243:(
233:·
226:·
219:·
212:·
185:.
121:)
115:(
110:)
106:(
96:·
89:·
82:·
75:·
48:.
25:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
