What defines a project scope?
The Project Scope pertains to the work necessary to deliver a product. Requirements and deliverables define the project scope, and it is critical that the stakeholder is in agreement with the information discussed in the proposed plan.
The use of mind mapping software such as MindView can greatly assist in the processes involved in creating the Project Scope.
Key Concepts of a Project Scope
- Scope planning does not occur after only one planning session
- The scope baseline consists of the project scope statement, WBS, and WBS dictionary
- A collaborative approach is the most effective method for scope planning
- All stakeholders must understand the scope baseline to minimize scope creep during project execution
Scope planning is a critical step to define the project scope including requirements and deliverables to establish the scope baseline. The scope baseline includes the project scope statement, work breakdown structure, and wbs dictionary. Tools and techniques to define the scope of work may include interviews with subject matter experts, brainstorming sessions, and workshops.
Project scope includes requirements and deliverables which are defined by the work breakdown structure and WBS Dictionary. Deliverables are outputs of the work performed to achieve the product, service, or result. Requirements are the features and characteristic of the project scope and may address project objectives, deliverables, product design and testing.
It is critical to a projects success that you define the project scope and requirements. This minimizes scope creep during project execution. Project scope is typically defined by stakeholder and scope inputs including the project charter, scope of work, scope statement and requirements documentation.
6 Sections of a Project Scope Statement
The Scope Statement is an essential part of any project and is used to outline the results the project will produce and the terms and/or conditions under which the work will be performed.
It is critical that you justify "how and why" your project came to be. Clearly describe the business need(s) it addresses as well as the scope of work to be performed. It is important to address how the project will affect and be affected by the other related activities.
Objectives are concrete statements describing what the project is trying to achieve. The objective should be written at a lower level, allowing it to be evaluated at the conclusion of a project to see whether it was achieved. Using the (SMART) method will assist in creating a well-worded objective.
Specific, Measurable, Attainable/Achievable, Realistic and Time-bound (SMART).
Product Scope Description
Scope Description is the features and functions of the products, services, and/or results your project will produce. It is important to mention that the Project Scope is more work-oriented, (the how's,) while Product Scope is more oriented toward functional requirements, (the what's.)
Product Acceptance Criteria
Acceptance Criteria are the standards required to satisfy the customer's quality expectations and gain acceptance of the final product. This can be summarized as the process and criteria for accepting completed products, services, or results. The Acceptance Criteria forms the basis for the Project Quality Plan
Here are some criteria that should be considered:
- Target dates
- Major functions
- Capacity, accuracy and availability
- Repair times
- Development costs
- Running costs
Constraints define the various restrictions that limit what, when and how you will achieve the goal as well as how much achieving it can cost.
There are three types of project constraints:
- Technological - relate to the sequence in which individual project activities must be completed.
- Resource - relate to the lack of necessary resources which may force parallel activities to be performed in sequence.
- Physical - caused by contractual or environmental conditions
The primary purpose is to identify the possible causes of delaying the completion of the project.
Assumptions are statements that we believe to be true and how you will address uncertain information as you conceive, plan, and perform your project. Assumptions are identified to add potential risk to a project even though they may turn out to be false. Assumptions can impact any part of a project life cycle, so it is important to document and analyze them.