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.
For more about scope creep, see "Ground Level Sources of Scope Creep," Point Lookout for July 18, 2012; "The Perils of Political Praise," Point Lookout for May 19, 2010; "More Indicators of Scopemonging," Point Lookout for August 29, 2007; "Scopemonging: When Scope Creep Is Intentional," Point Lookout for August 22, 2007; "The Deck Chairs of the Titanic: Strategy," Point Lookout for June 29, 2011; and "The Deck Chairs of the Titanic: Task Duration," Point Lookout for June 22, 2011.
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. More info
Your comments are welcomeWould you like to see your comments posted here? rbrenXMkwGAWcVbijgskrner@ChachGCdRgLNAMbQsIdyoCanyon.comSend 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.
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:
- See No Evil
- When teams share information among themselves, they have their best opportunity to reach peak performance.
And when some information is withheld within an elite group, the team faces unique risks.
- The Injured Teammate: II
- You're a team lead, and one of the team members is suddenly very ill or has been severely injured. How
do you handle it? Here are some suggestions for breaking the news to the team.
- Risk Management Risk: I
- Risk Management Risk is the risk that a particular risk management plan is deficient. It's often overlooked,
and therefore often unmitigated. We can reduce this risk by applying some simple procedures.
- Ground Level Sources of Scope Creep
- We usually think of scope creep as having been induced by managerial decisions. And most often, it probably
is. But most project team members — and others as well — can contribute to the problem.
- Down in the Weeds: II
- To be "down in the weeds,' in one of its senses, is to be lost in discussion at a level of detail
inappropriate to the current situation. Here's Part II of our exploration of methods for dealing with
this frustrating pattern so common in group discussions.
See also Project Management for more related articles.
Forthcoming issues of Point Lookout
- Coming May 31: Unresponsive Suppliers: III
- When suppliers have a customer orientation, we can usually depend on them. But government suppliers are a special case. Available here and by RSS on May 31.
- And on June 7: The Knowledge One-Upmanship Game
- The Knowledge One-Upmanship Game is a pattern of group behavior in the form of a contest to determine which player knows the most arcane fact. It can seem like innocent fun, but it can disrupt a team's ability to collaborate. Available here and by RSS on June 7.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenBJzXxUQpRkrwXGvPner@ChackYpWQrnXESmPoueqoCanyon.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:
- Get 2001-2 in Geese Don't Land on Twigs (PDF, USD 11.95)
- Get 2003-4 in Why Dogs Wag (PDF, USD 11.95)
- Get 2005-6 in Loopy Things We Do (PDF, USD 11.95)
- Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, USD 11.95)
- Get 2009-10 in The Questions Not Asked (PDF, USD 11.95)
- Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, USD 28.99)
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
- Creating High Performance Virtual Teams
- Many people experience virtual teams as awkward, slow, and sometimes
frustrating. Even when most team members hail from the same nation or culture, and even when they all
speak the same language, geographic dispersion or the presence of employees from multiple enterprises
is often enough to exclude all possibility of high performance. The problem is that we lead, manage,
and support virtual teams in ways that are too much like the way we lead, manage, and support co-located
teams. In this program, Rick Brenner shows you how to change your approach to leading, managing, and
supporting virtual teams to achieve high performance using Simons' Four Spans model of high performance.
Read more about this program. Here's an upcoming date
for this program:
- Baci Grill, 134 Berlin
Road, Berlin, CT 06416: September 19,
Monthly Meeting, Southern New England Chapter of the Project Management Institute. Register now.
- Baci Grill, 134 Berlin Road, Berlin, CT 06416: September 19, Monthly Meeting, Southern New England Chapter of the Project Management Institute. Register now.
- 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 organizational leaders, business
analysts, project sponsors, and project managers, the story is fascinating. Lessons abound. Read
more about this program. Here's an upcoming date for this program:
- CTCPA, 716 Brook Street,
Rocky Hill, CT 06067: September 20,
Full-day Workshop, Southern New England Chapter of the Project Management Institute. Register now.
- CTCPA, 716 Brook Street, Rocky Hill, CT 06067: September 20, Full-day Workshop, Southern New England Chapter of the Project Management Institute. Register now.
- Your stuff is brilliant! Thank you!
- You and Scott Adams both secretly work here, right?
- I really enjoy my weekly newsletters. I appreciate the quick read.
- A sort of Dr. Phil for Management!
- …extremely accurate, inspiring and applicable to day-to-day … invaluable.