« Managing Projects in the Cloud Simply Makes Sense
Agile Lifecycles for Geographically Distributed Teams, Part 1 »

Project “Scope Creep” - Chaos Unleashed

April 29, 2012 | Author: PM Hut | Filed under: Project Scope Management, Scope Management

Project “Scope Creep” - Chaos Unleashed
By Douglas E. Castle

Projects are generally implemented in stages, and their components are compartmentalized, with each department (or individual) expected to focus on some specific, well-defined scope of responsibilities. When one individual treads out of his or her scope, and into another individual’s, this is what Project Managers refer to as “scope creep.” It invariably creates a breakdown in systems, procedures and progress. It causes crossed wires, confusion and a wonderful textbook case of the Law Of Diminishing Returns.

Its usual causes are several:

  1. Intellectual curiosity and a need to “share” or “meddle”.

  2. A lack of trust or faith in the ability, work ethic or intentions of one or more of the project team members by some other member or members.

  3. A poorly-defined scope and separation of responsibilities, or of project phases.

These can be either prevented or minimized by several means:

  1. Carefully and clearly define the scope of responsibility and principal focus of each project team participant;

  2. Be certain that a member of the team is a coordinating communications and liaison officer — a person through whom any “ultra-scope” ideas must be presented before being discussed with other team members. This tends to discourage creepage, but serves as a means of aggregating (capturing) some ideas which may prove useful;

  3. The Project Manager should remind each of the team members of his or her principal focus, scope and function at regular intervals to prevent straying from the planned path, and to minimize the temptations or incentives to chaotic creeping.

A culture of mutual respect and trust amongst the project team should be fostered, and some periodic forum should be devised where team members can creep a bit in the interest of brainstorming and bonding. That’s actually healthy.

Douglas Castle is a senior level expert in all matters of high-level corporate negotiations, deal structure, and strategic planning. He speaks, consults and writes frequently about these subjects, as well as about key aspects of leadership and crisis management.

Mr. Castle has been, and continues to be a seasoned and acclaimed advisor, director and trustee to emerging enterprises and growing companies worldwide, across a broad variety of industries on matters of organizational development, strategic planning, financing (both institutional equity and debt), international incorporations and negotiating of co-ventures, mergers and acquisitions. Mr. Castle’s current passions are centered upon leveraging his wealth of experience in high-stakes corporate negotiations, deal structure, organizational engineering, strategic planning and financing to foster innovation and entrepreneurial growth and success. You can read more from Douglas on his professional blog and personal blog.

Share this article:
  • Facebook
  • LinkedIn
  • TwitThis

This entry was posted on Sunday, April 29th, 2012 and is filed under Project Scope Management, Scope Management. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

No comments yet.

feel free to leave a comment

Comment Guidelines: Basic XHTML is allowed (a href, strong, em, code). All line breaks and paragraphs are automatically generated. Off-topic or inappropriate comments will be edited or deleted. Email addresses will never be published. Keep it PG-13 people!

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

All fields marked with " * " are required.

The Stevens Enterprise Project Management Master's Program

Project Management Categories