Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 22, Issue 17;   May 4, 2022: Rational Scope Management

Rational Scope Management

by

In project management, rational, responsible scope management helps us focus on the task at hand. But rational scope management lets us adapt our work to changes in external factors, and changes in our understanding of the problem.
A sturdy fence with a working gate

A sturdy fence with a working gate. A metaphor for rational scope management is a sturdy fence with multiple gates. To manage scope rationally, we want some flexibility, but flexibility within certain bounds. Metaphorically, the scope definition is the fence. The gates in the fence are the passages that enable users to redefine the defined scope. We want to be able to pass through the fence, but only when we meet certain conditions, and only under appropriate supervision. Image by Momental courtesy Pixabay.com.

Decades ago, if the definition of a project's scope was clear enough, it helped keep the project team more or less focused on the task at hand. From time to time, when we weren't watching closely enough, or when organizational politics intervened, a project's scope might stealthily "creep" to include some activity that wasn't intended from the outset. When that happened, we adapted. To keep it from happening again, we created project governance. Governance procedures began to require project scope statements that included elements such as Goals and Objectives, Requirements, Not-Requirements, Tasks, Deliverables, Resources, and even Change Procedures.

But Changes in the environment, or markets,
or customer expectations, or even our
understanding of the problem bring
about changes in scope
in today's rapidly changing environments, we rarely know enough at the outset about these elements to provide adequate control of scope. Projects are now so complicated that by the time we've defined a project's scope, we need to change the definition. Changes in the environment, or markets, or customer expectations, or even our understanding of the problem bring about changes in scope. We no longer strive to control scope; we now seek to manage it.

Augmenting project scope statements

Project governance processes are designed to deal with entire organizations. They must address projects of all kinds, in various states of development. The general problem of controlling the scope of such a heterogeneous project population requires a general solution. And that general solution has inherent difficulties in exploiting the particulars of each target project.

In part, the difficulty in managing scope traces to the attempt to deal with rapidly changing scope of every kind of project in every state of development using only general language. To address this difficulty, we must find ways to augment scope statements using specific knowledge about the projects themselves.

Ambiguity reduction by example

One approach to reducing the ambiguity of very general scope statements involves including examples of in-scope and not-in-scope.

In many cases, scope is not well-defined in the mathematical sense. That is, the definition of the term within scope for any given project might have more than one interpretation. For this reason, although devising a scope definition to control the scope of a project is necessary, it isn't sufficient. We must add to the definition explicit limiting examples of what is within scope and what is not, using what we know about the debates that led to the definition.

When we include examples, the differing interpretations of the project scope statement must take the examples into account. The examples of what is within scope — and examples of what is not within scope — then serve to limit the "ambiguity radius" of the rest of the scope statement.

Three guidelines for constructing limiting examples

Examples do serve to clarify the scope statement, but they also serve to limit political influence on scope. Some politically powerful individuals succeed in expanding scope by making out-of-scope promises on behalf of the organization. Including their likely promises in the list of out-of-scope examples can deter such promises. The deterrence effect is especially strong when the individuals involved have reviewed and approved the scope statement.

Here are three categories of examples of out-of-scope capabilities that can be included in scope statements.

Whatever people were disappointed about being excluded
Track the capabilities that were once proposed for inclusion in scope, but which were ultimately excluded. That will produce a list of items that are at greatest risk of being included in the project at some later stage.
Wherever scope has expanded in the past
A second class of high-risk capabilities includes those that were within scope of other projects, either in the past or underway, but which have been removed for one reason or another. Whatever forces were at work to have these capabilities included at first might still be active.
Past incidents of secret scope creep
Some scope expansion comes about as a result of actions taken by project team members on their own initiative. They don't consult team members or team leads in advance; they just perform the work privately. To limit this effect, include examples of "secret scope creep" that clearly illustrate the practice. If you're aware of initiatives that some have been advocating, use these as explicit examples of out-of-scope activity.

Last words

Small size is among the stronger arguments supporters of scope expansion use to advocate items for inclusion in scope. But the size of a scope expansion isn't determined by what's contemplated for inclusion in the present project. Rather, the size of a scope expansion is determined by the size of the ongoing commitment it implies, in every aspect of future support. For products or services, this can include everything from introduction to retirement. The scale of this commitment, not the scale of the current scope expansion, determines what is at stake when making scope expansion decisions. Go to top Top  Next issue: Capability Inversions and Workplace Abuse  Next Issue

How to Spot a Troubled Project Before the Trouble StartsProjects never go quite as planned. We expect that, but we don't expect disaster. How can we get better at spotting disaster when there's still time to prevent it? How to Spot a Troubled Project Before the Trouble Starts is filled with tips for executives, senior managers, managers of project managers, and sponsors of projects in project-oriented organizations. It helps readers learn the subtle cues that indicate that a project is at risk for wreckage in time to do something about it. It's an ebook, but it's about 15% larger than "Who Moved My Cheese?" Just . Order Now! .

Your comments are welcome

Would you like to see your comments posted here? rbrenubcqSvusyBsQaEDwner@ChacfhuriyFKgDguTpuYoCanyon.comSend me your comments by email, or by Web form.

About Point Lookout

This article in its entirety was written by a 
          human being. No machine intelligence was involved in any way.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.

This article in its entirety was written by a human being. No machine intelligence was involved in any way.

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.

Related articles

More articles on Project Management:

Eastern Redcedar in crossection, with white sapwood on the outside edges, and red to deep reddish-brown heartwoodThe Retrospective Funding Problem
If your organization regularly conducts project retrospectives, you're among the very fortunate. Many organizations don't. But even among those that do, retrospectives are often underfunded, conducted by amateurs, or too short. Often, key people "couldn't make it." We can do better than this. What's stopping us?
Gachi Fernandez and Sergio Cortazzo, professional tango coupleScope Creep, Hot Hands, and the Illusion of Control
Despite our awareness of scope creep's dangerous effects on projects and other efforts, we seem unable to prevent it. Two cognitive biases á#8212â the "hot hand fallacy" and "the illusion of control" á#8212â might provide explanations.
Three simple carabinersTeam Risks
Working in teams is necessary in most modern collaborations, but teamwork does carry risks. Here are some risks worth mitigating.
Gen. Douglas MacArthur (left) and Willie Keeler (right)Ten Approaches to Managing Project Risks: II
Managing risk entails coping with unwanted events that might or might not happen, and which can be costly if they do happen. Here's Part II of our exploration of coping strategies for unwanted events.
The deadline at Rock Island Prison during the U.S. Civil WarIrrational Deadlines
Some deadlines are so unrealistic that from the outset we know we'll never meet them. Yet we keep setting (and accepting) irrational deadlines. Why does this happen?

See also Project Management and Project Management for more related articles.

Forthcoming issues of Point Lookout

Pair of Wooden Shoes [right] (Sabots)Coming June 4: White-Collar Contractor Sabotage
Modern firms in competitive, dynamic markets draw on many types of employer/employee relationships, including contractors. By providing privileges and perks preferentially among these different types, they risk creating a caldron of resentments that can reduce organizational effectiveness. Available here and by RSS on June 4.
Horse Shoe Bend of the Colorado River in the Grand CanyonAnd on June 11: More Things I've Learned Along the Way: VI
When I gain an important insight, or when I learn a lesson, I make a note. Example: If you're interested in changing how a social construct operates, knowing how it came to be the way it is can be much less useful than knowing what keeps it the way it is. Available here and by RSS on June 11.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenubcqSvusyBsQaEDwner@ChacfhuriyFKgDguTpuYoCanyon.com or (650) 787-6475, 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-1000 words in your inbox in one hour. License any article from this Web site. More info

Follow Rick

Send email or subscribe to one of my newsletters Follow me at LinkedIn Follow me at Bluesky, or share a post Subscribe to RSS feeds Subscribe to RSS feeds
The message of Point Lookout is unique. Help get the message out. Please donate to help keep Point Lookout available for free to everyone.
Technical Debt for Policymakers BlogMy blog, Technical Debt for Policymakers, offers resources, insights, and conversations of interest to policymakers who are concerned with managing technical debt within their organizations. Get the millstone of technical debt off the neck of your organization!
Go For It: Sometimes It's Easier If You RunBad boss, long commute, troubling ethical questions, hateful colleague? Learn what we can do when we love the work but not the job.
303 Tips for Virtual and Global TeamsLearn how to make your virtual global team sing.
101 Tips for Managing ChangeAre you managing a change effort that faces rampant cynicism, passive non-cooperation, or maybe even outright revolt?
101 Tips for Effective MeetingsLearn how to make meetings more productive — and more rare.
Exchange your "personal trade secrets" — the tips, tricks and techniques that make you an ace — with other aces, anonymously. Visit the Library of Personal Trade Secrets.
If your teams don't yet consistently achieve state-of-the-art teamwork, check out this catalog. Help is just a few clicks/taps away!
Ebooks, booklets and tip books on project management, conflict, writing email, effective meetings and more.