Project Scope Management: What It is and Why It’s Important?
George LewisProgram/Project Manager| DXC Technology CompanyHeredia, Costa Rica
What It is and Why It’s Important? Saving Changes...
Sort By:
Aleksei NikitinLead expert| Higher School of EconomicsSaint-Petersburg, Russian Federation
In IT projects, this is the most important set of activities. It includes definition, planning, measurement, very frequent (daily) corrections and clarifications, and acceptance regarding:
1) the product of the project (most importantly)
2) the work required to obtain the product (second priority)
3) auxiliary works, such as refactoring, reengineering, management etc. (third priority).
Scope is the basis of the project, other parameters are built from it: cost, timing, risks, quality, etc.
Changing any element of scope (both product and work) can lead to significant changes in cost and schedule.
In the context of IT projects, the scope changes or tries to change every moment, so a systematic approach to management is required. I usually try to aquire a dedicated analyst to manage the product scope for the whole duration of the project. Saving Changes...
The "what it is" isn't as interesting as the "why it's important" question. Without scope management, you don't have a project - you have a set of related activities being performed with no guarantee of a meaningful outcome.
Kiron Saving Changes...
RAJESH K LProject Manager, PMP| Bharat Electronics, Bengaluru, IndiaBengaluru, Karnataka, India
Agree with Aleksei,
In my view Scope of Project and its Management is at the core of Project. Saving Changes...
Tamer Zeyad SadiqAssistant Cost Manager| Turner & TownsendRiyadh, Ar Riyad, Saudi Arabia
The scope is a project constraint!!! Before the project starts, there is should be high level of scope in project charter before authorize project start. The project will not start without the requirements and the scope!!! Saving Changes...
Aleksei NikitinLead expert| Higher School of EconomicsSaint-Petersburg, Russian Federation
It is very interesting that in PMBOK process table (table 1-4) there is no Scope Management in the Executing Process Group. I think that is very "waterfall-ish". It means we plan everything in planning process and then execute according to those plans (with rare exceptions of change requests). In my experience the work of redefining, clarifying, changing and verifying the Scope (both product and project) is an ongoing everyday process.
...
1 reply by Julien Cottin
Jul 20, 2018 10:00 AM
Julien Cottin
...
I guess the "daily routine" is about monitoring the scope/requirements coverage and adapting the PMP & its baselines if a scope change is required
I'll give you an actual example (paraphrased) of a requirement I once saw in one of our projects (military):
"The vehicle must be able to operate under all conditions, everywhere in the world".
If requirements are the building blocks of project scope, and scope management planning is also about managing stakeholders expectations about what the project will deliver, what then is the impact of this requirement to the scope to the project? Saving Changes...
It is very interesting that in PMBOK process table (table 1-4) there is no Scope Management in the Executing Process Group. I think that is very "waterfall-ish". It means we plan everything in planning process and then execute according to those plans (with rare exceptions of change requests). In my experience the work of redefining, clarifying, changing and verifying the Scope (both product and project) is an ongoing everyday process.
I guess the "daily routine" is about monitoring the scope/requirements coverage and adapting the PMP & its baselines if a scope change is required Saving Changes...
