The process of collect requirements identifies all the essential requirements, but one can’t assure that all the requirements are mentioned or included in the project. But, the Define Scope process selects the final project requirements from the requirements documentation delivered during the Collect Requirements process. Hence, the project manager can develop a detailed description of the project and product which is called the Project Scope Statement.
Define Scope is a process of developing a detailed description of the project and product. The key benefit of the Define Scope process is that it describes the project's boundaries by defining which of the requirements collected will be included in the project.
The project charter is a document that provides the high-level project description and product characteristics. It also enlists all the project approval requirements. If a project charter is not being used to its fullest in any organization, then comparable information needs to be developed and used as a basis for the detailed project scope statement. In situations where the organizations do not produce a formal project charter for setting out common goals, rules and regulations they will usually perform an informal analysis to identify the content necessary for further scope planning.
Both project management and scope management plans have the same characteristics but whereas project management plan documents as to how the project scope will be defined, validated, and controlled.
Examples of project documents that can be listed as inputs for defining scope are as follows;
The role of the assumption log is to identify the assumptions and constraints about the project, product, stakeholders, environment and other factors that can influence the project and the product scope.
The process of identifying the list of requirements that are to be incorporated into the project scope.
The risk register mainly contains response strategies that may affect the project scope by reducing the project and the product scope to avoid or mitigate a risk that is to occur in the project.
The factors which can influence the Define Scope process include:
The factors that influence the Define Scope process include:
Policies, procedures, and templates for a project scope statement
Project files from previous projects
Lessons learned from previous phases and projects
With regards to the technique of expert judgment, one has always to consult a group or an individual who has exceptional knowledge in dealing with similar projects.
The best example of a data analysis technique that can be used in this process is alternatives analysis. This alternatives analysis helps in evaluating ways to meet the requirements and objectives that are identified in the project charter.
Multicriteria Decision Analysis is the best example of this particular process. Under this technique, a decision matrix is used to provide a systematic analytical approach for establishing necessities like requirements, schedules, budget, and resources to clarify the project and product scope further.
An example of interpersonal and team skills is facilitation process. This process is mainly used in workshops and sessions happening with key stakeholders who are always high on expectations. The ultimate goal of this process is to reach a cross-functional and shared understanding of the project deliverables.
Product analysis is used to define the products and services related to a particular project. The process includes asking questions about a product or service and generating answers to describe the use, characteristics, and other relevant aspects of what is going to be delivered.
The following are the examples related to the product analysis process:
Project Scope Statement is a detailed description of the project scope, which includes significant deliverables, assumptions, and constraints. It also documents the project scope and the product scope and describes the project’s deliverables and the work required to deliver them. Based on the level and degree of detail the project scope statement defines the work that will be performed, and the work that is minimized can help determine how well the project management team can control the overall project scope.
Product scope description
A method used to elaborate on the characteristics of the product that are defined in the project charter and requirements documentation.
A set of conditions that are required to be met before the final deliverables are accepted by the stakeholders.
Any unique and verifiable product that is required to be produced to complete a process, phase, or project.
A method to exclude the feasible products from the scope of the project to help the project manager to manage the stakeholder’s expectations.
|Project Charter||Project Scope Document|
|Project purpose||Project scope description (progressively elaborated)|
|Measurable project objectives and related success criteria||Project deliverables|
|High-level requirements||Acceptance criteria|
|High-level project description, boundaries, and key deliverables||Project exclusions|
|Overall project risk|
|Summary milestone schedule|
|Preapproved financial resources|
|Key stakeholder list|
|Project approval requirements (i.e., what constitutes success, who decides the project is successful, who signs off on the project)|
|Project exit criteria (i.e., what are the conditions to be met to close or to cancel the project or phase)|
|Assigned project manager, responsibility, and authority level|
|Name and authority of the sponsor or another person authorizing the project charter|
The role of assumption log at this stage is to update the log with additional assumptions or constraints which were identified during the project process.
The documentation that consists of all of the stakeholder's requirements that are to be met and also registers the important deliverables that are in the pipeline of the project manager.
A method that is used to record the requirements of a particular project. This documentation will keep of all the deliverables that are met and the other deliverables that are to be accomplished by the project manager.
Requirements Traceability Matrix
A method that is used to compare the project's scope, requirements and deliverables are all the same when they are compared with the project's baseline that was created during the project management plan.
The Define Scope process takes the high-level product descriptions, assumptions, and constraints, which were documented in the Develop Project Charter process during the initiating process group, and develops from them a more detailed description of the scope in the Project Scope Statement. The project scope may not be entirely defined during the initial stage of determining the scope.
Aspects like additional risks, assumptions, and constraints arise during the project execution, so the project scope may be revised or updated as necessary as part of the iterative process of developing the project scope. The define scope process is a lengthy process that commences atop from the high-level requirements to detailed requirements of the stakeholders’ and are translated into significant deliverables. These major deliverables are set as the primary objectives for the project management team, and the team is asked to fulfill these requirements.
Know more about project management best practices through Invensis Learning’s Project Management certification training on PMP, CAPM, PRINCE2, Project Management Fundamentals, P3O, and MSP. We are a trusted training partner for Fortune 500 companies and Government institutions globally. For on-site group training, please e-mail us at firstname.lastname@example.org.