Some Causes of Scope Creep
by Rick Brenner
When we suddenly realize that our project's scope has expanded far beyond its initial boundaries — when we have that how-did-we-ever-get-here feeling — we're experiencing the downside of scope creep. Preventing scope creep starts with understanding how it happens.
Mort finally got to the punch line. "We just didn't anticipate the difficulties of the consolidation," he said, "and now it looks like we'll have to take a three-month hit."
Just last quarter, Jack had okayed the consolidation of Marigold into Metronome, based on the promise of schedule savings from eliminating duplications and from better coordination. Now he sat stunned, wondering how they had reached such familiar territory so quickly.
By consolidating the two projects, Jack had unwittingly expanded their scope, because the combined team suddenly had a new task: consolidation. They became victims of a problem that afflicts many projects — scope creep.
To manage scope creep, begin by understanding its causes. Here are some of the more common sources of scope creep.
- The unknown
- Projects are ventures into unknown territory. Sometimes we underestimate the complexity of the problem we've tackled.
- We sometimes forget that good enough is good enough.
- Placating conflict
- We'll do almost anything to avoid dealing with conflict directly. We'll even expand project scope to satisfy all conflicting parties. When we placate conflict, we create a project that nobody can execute.
We sometimes forget
that good enough
is good enough
- To secure resources, a failing project sometimes acquires another project on the basis of "natural fit" or "efficiencies." But consolidation isn't free, and the efficiencies are often illusory.
- Career advancement
- By commandeering more resources, the sponsors or leaders of a project can enhance their organizational power. Senior managers must learn to recognize these tactics, and approve scope expansions only on the basis of sound management principles.
- Lies and self-deception
- Sometimes we lie to others or deceive ourselves about what's really involved. We can do this to secure approval for the project, or to persuade ourselves or the implementing organization to agree to tackle it. Lying to others is unethical. When it occurs, the perpetrators must be held accountable. Deceiving oneself is tragic.
- The union of all misunderstandings
- If scope isn't clearly defined at the outset, misunderstandings result. When that happens, to preserve consensus that the project should continue, we might have to expand the project scope to include the union of all initial understandings. Making things painfully clear at the outset is worth the effort.
- The Donald Crowhurst effect
- Donald Crowhurst was a participant in the 1968 round the world single-handed sailing race sponsored by the London Sunday Times. As described in a 1970 book by Nicholas Tomalin and Ron Hall, his life pattern was to tackle ever-larger projects, concealing a pattern of failure. Like Donald Crowhurst, some projects expand their scope to avoid acknowledging failure. Failure or restart must be realistic options for any project manager.
Do you know which of your projects are afflicted with scope creep? How did they get there? Top Next Issue
If you're dealing with scope creep, The Strange Last Voyage of Donald Crowhurst
is a captivating read.
Is every other day a tense, anxious, angry misery as you watch people around you, who couldn't even think their way through a game of Jacks, win at workplace politics and steal the credit and glory for just about everyone's best work including yours? Read 303 Secrets of Workplace Politics, filled with tips and techniques for succeeding in workplace politics. Order Now!
Your comments are welcome
Would you like to see your comments posted here? Send me your comments by email
, or by Web form
About Point Lookout
Thank you for reading this article. I hope you enjoyed it and found it useful,
and that you'll consider recommending it to a friend
Point Lookout is a free weekly email newsletter. Browse the archive
of past issues. Subscribe for free.
Support Point Lookout by joining the Friends of Point Lookout,
as an individual or as an organization.
Do you face a complex interpersonal situation? Send it in,
anonymously if you like, and I'll give you my two cents.
More articles on Project Management
- Team Thrills
- Occasionally we have the experience of belonging to a great team. Thrilling as it is, the experience is rare. How can we make it happen more often?
- My Right Foot
- There's nothing like an injury or illness to teach you some life lessons. Here are some things I learned recently when I temporarily lost some of my independence.
- The True Costs of Cost-Cutting
- The metaphor "trimming the fat" rests on the belief that some parts of the organization are expendable, and we can remove them with little impact on the remainder. Ah, if only things actually worked that way...
- The Politics of Lessons Learned
- Many organizations gather lessons learned — or at least, they believe they do. Mastering the political subtleties of lessons learned efforts enhances results.
- The Politics of the Critical Path: Part II
- The Critical Path of a project is the sequence of dependent tasks that determine the earliest completion date of the effort. We don't usually consider tasks that are already complete, but they, too, can experience the unique politics of the critical path.
See also Project Management for more related articles.
I offer email and telephone coaching at both corporate and individual rates.
Contact me for details at rbrenner@ChacoCanyon.com
or (617) 491-6289, or toll-free in the continental US at (866) 378-5470.
Get the ebook!
Past issues of Point Lookout
are available in six ebooks:
Reprinting this article
Are you a writer, editor or publisher on deadline?
Are you looking for an article that will get people talking and get compliments flying your way? You can have 500 words in your inbox in one hour. License any article from this Web site. More info
- The Race to the South Pole: Ten Lessons for Project Managers
- On 14 December 1911, four men led by Roald Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished. As historical drama, why this happened is interesting enough, but to project managers, the story is fascinating. Lessons abound. Read more about this program. Here's an upcoming date for this program:
- The Race to the South Pole: The Power of Agile Development
- On 14 December 1911, four men led by Roald Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished. As historical drama, why this happened is interesting enough. Lessons abound. Among the more important lessons are those that demonstrate the power of the agile approach to project management and product development. Read more about this program. Here's an upcoming date for this program: