3362 Registered Users
Skip Navigation LinksHome > ITTO Section > Project Scope Management > Define Scope

Introduction


- Define Scope Process deals with setting the project boundaries in terms of deciding the inclusions and exclusions among all the requirements collected.
- Define Scope Process decides on the project and product scope.
- Define Scope is a highly iterative process because multiple factors are dependent on it because scope of part of the triple constraints. It is also one of the most important processes in deciding the project success.

Inputs


- Scope Management Plan: The Scope Management Plan provides guidance for different processes in Scope knowledge area. Scope Management Plan specifies what amount of detail must be in the scope statement and how scope will be defined.
- Project Charter: The Project Charter is used to pick product description, assumptions and constraints defined at the high-level to build the scope statement further.
- Requirements Documentation: This has the requirement list as well as the requirements priority for the project as listened from different customers. Based on this, the actual scope can be defined. While project charter acts as the guiding principle in terms of looking at other constraints along with the high-level product characteristics, the requirement documentation provides the specific project requirements helping to decide on the actual project scope.
- Organizational Process Assets: Templates for closure as well as policies and procedures relevant to project or phase closure.

Tools & Techniques


- Expert Judgment: Leverage experience from SMEs or other project managers or consultants.
- Product Analysis: Since this process involves defining the product scope, it involves analysis of product features based on similar products or models already developed. Product analysis would involve product breakdown, value engineering and requirements analysis.
- Facilitated Workshops: In case of workshops, the end-users and the design / development team sit together to understand the requirements called VoC (Voice of Customer) and coming out with the best possible solution. It is also called as JAD or QFD based on the industry. While Focus Groups are moderated by a mediator, workshops are discussions among cross-functional team aimed at consensus based on priorities. Although this is a technique used in collect requirements process, since this process deals with requirement analysis, a cross-functional team will help.
- Alternatives Generation: Since scope is based on different other project constraints, there is a need to look at different alternatives fitting the current requirement on hand.

Outputs


- Project Scope Statement: Project scope statement includes the following –
> Product Description
> Constraints
> Assumptions
> Deliverables
> Exclusions
> Acceptance Criteria

While project charter deals at a high-level since it is provided by the project sponsor, scope statement is a project-level document with more details and that too aimed at project and product scope.
- Project Documents Updates: While detailing the scope, there might be a need to update some of the other documents created in the project so far, which might include the requirement documentation or requirement traceability matrix and so on.

Match the Following


1. Scope Statement - a. Industry groups
2. Project Charter - b. Inclusions and Exclusions
3. Facilitated Workshop - c. How-To Define Scope
4. Scope Management Plan - d. Tool
5. Expert Judgment – e. High-Level Details

Match the Following (Answers)


1. Scope Statement - b. Inclusions and Exclusions
2. Project Charter - e. High-Level Details
3. Facilitated Workshop - d. Tool
4. Scope Management Plan - c. How-To Define Scope
5. Expert Judgment – a. Industry groups