introduction
welcome to first article of knowledge Area ((Scope Management))
Project scope management refers to the total amount of work that must be done in order to deliver a product, service, or result with specified functions and features.
It includes everything that must go into a project, as well as what defines its success.
Without a comprehensive project scope management plan, there’s a RISK your team is doing work that’s unnecessary to complete the project at hand or even wasting time thinking about what they should be doing next.
what is project scope
before diving inside scope management >>> we need to to understand What is Project Scope?
Project Scope is the work that needs to be accomplished to deliver a product, service, or result with the specified features and functions. Scope refers to the detailed set of deliverables or elements of a project; these deliverables are derived from a project’s requirements.
Project Scope Management consists of :
- Planning: The process of getting an overview and defining the work that needs to be done to achieve the deliverables is called Planning.
- Controlling: process of documenting, tracking, focusing on scope disruption and also continually approving and disapproving the project changes through controlling and monitoring process is called controlling.
[Project Scope] vs [Product Scope ]
The two most widely used terms in Project Management are Project Scope and Product Scope.
Product Scope:
- Product scope can be defined as the features or characteristics of a product regardless of the design, function or parts, and the critical point is that product scope refers to the actual tangible product that is finally produced.
Project Scope:
- In contrast to product scope, project scope focuses on the various steps taken to deliver a product. Project scope can include, things like assembly lines, budgets, staff training, and supply chains and personnel allocations.
Scope Management Concepts
the Concepts
- Scope management is defining what work is required and make sure all work is DONE (only work NOT extra )
- Project manager must plan in advance how will determine scope and to manage and control it
- Scope management plan is iterated during project planning
- Scope must clearly defined and obtain formal acceptance before work start
- Requirements should be gathered from all stakeholder who are defined in stakeholder register NOT only key stakeholders in project charter
- Gold plating (extra work ) is NOT allowed
- Any change to scope must be evaluated to effect to other areas like time ,cost, quality , risk , customer satisfaction
- NO change to scope is allowed without approved change request
- Any change to scope is NOT allowed if it NOT fit with project charter
Scope Management Processes
5.1 Plan Scope Management (Planning)
- develop plan how you will plan , manage and control scope and requirements on the project
5.2 Collect Requirements (Planning )
- Determine requirements and make sure all requirement support business case that stated in project charter
5.3 Define Scope (Planning )
- Sort and balance requirements to determine project scope
5.4 Develop Work Breakdown Structure WBS (Planning )
- Break down scope to smaller and manageable pieces , and define each piece in WBS dictionary
5.5 Validate Scope (Monitoring & Controlling )
- Obtain validation that completed scope is work and acceptable by customer
5.6 Control Scope (Monitoring & Controlling )
- Measure scope performance and adjust it as needed
Conclusion
this was briefly an overview a bout project scope management which known as chapter 5 after integration management
next article in networks pioneers >> we will details each one of six process for scope management
please join us
