Project Scope Management

Collecting Requirements

Collecting requirements is the process of defining and documenting stakeholders needs to meet the project objectives. The projects success is directly influenced by the care taken in capturing and managing project and product requirements. Requirements include the quantified and documented needs and expectations of the sponsor, customer, and other stakeholders.

Category of requirements
Project requirements it includes business requirements, project management requirements, and delivery requirements. Product Requirements it includes information on technical requirements, security requirements, performance requirements.

Collect requirements: Inputs

Project Charter Used to provide the high-level project requirements and highlevel product description of the project so that detailed product requirements can be developed. Stakeholder Register It is used to identify stakeholders that can provide information on detailed project and product requirements

Collect requirements: Tools and Techniques

Interviews It a formal or informal approach to discover information from stakeholders by talking to them directly Focus Groups It brings together prequalified stakeholders and subject matter experts to learn about their expectations and attitudes about a proposed product, service, or a result

 Facilitated Workgroups - Workshops are considered a primary technique for quickly defining cross-functional requirements and reconciling stakeholder differences. Group Creativity Techniques Brainstorming Nominal group techniques The Delphi Technique Idea/mind mapping Affinity diagram

 Group Decision Making Techniques Group decision making is an assessment process of multiple alternatives with an expected outcome in the form of future actions resolution. It can be used to generate, classify, and prioritize product requirements.
Unanimity Majority Plurality Dictatorship

 Questionnaires and Surveys Observations Prototypes - prototyping is a method of obtaining early feedback on requirements by providing a working model of the expected product before actually building it.

Collect Requirements: Outputs

Requirement Documentation Requirements documentation describes how individual requirements meet the business need for the project.
Components of requirement documentation can include, but, are not limited to:

Business need or opportunity to be seized, describing the limitations of the current situation and why the project has been undertaken Business and project objectives for traceability Functional requirements Non- functional requirements

Quality requirements Acceptance criteria Business rules stating the guiding principles of the organization Impacts to other organizational areas Impacts to other entities Support and training requirements Requirements assumptions and constraints

 Requirements Management Plan The requirements management plan documents how requirements will be analyzed documented and managed through the project. Components: How requirements activities will be planned, tracked, and reported. Configuration management Requirements prioritization process Product metrics that will be used Traceability structure

 Requirements Traceability Matrix Table that links requirements to their origin and traces them throughout the project life cycle.
This process includes, but is not limited to tracing:

Requirements to business needs, opportunities, goals, and objectives Req. to project objectives to project scope/wbs deliverables to product design to product development to test strategy and test scenarios High-level req. to more detailed req.

Define Scope

 Define Scope is the process of developing a detailed description of the project and product. The preparation of a detailed project scope statement is critical to project success and builds upon the major deliverables, assumptions, and constraints that are documented during project initiation. Existing risks, assumptions, and constraints are analyzed for completeness.

Define Scope: Inputs

Project Charter Provides high-level project description and product characteristics; also constrains project approval requirements. Requirements Documentation Organizational Process Assets
Policies, procedures, and templates for a project scope statement. Project files from previous projects, and Lessons learned from previous phase or projects.

Project Scope: Tools and Techniques

Expert Judgment Used to analyze the information needed to develop the project scope statement. Product Analysis For projects that have a product as a deliverable, as opposed to a service or result product analysis can be an effective tool.

 Alternative Identification is a technique used to generate different approaches to execute and perform the work of the project. Facilitated Workshops

Define Scope: Outputs

Project Scope Statement
Product Scope Description Progressively elaborates the characteristics of the product, service, or result described in the project charter and requirements. Product Acceptance Criteria Defines the process and criteria for accepting completed products, services, or results.

 Project deliverables - Deliverables include both the outputs that comprise the product or service of the project. And the deliverables may be described at a summary level or in great detail. Project exclusions - Generally identifies what is excluded as from the project. Explicitly stating what is out of scope for the project helps on manage stakeholders expectations.

 Project constraints - Lists and describes the specific project constraints associated with the project scope that limits the teams options.

Verify Scope

Verify Scope is the process of formalizing acceptance of the completed project deliverables. Verify Scope Includes reviewing deliverables with the customer or sponsor to ensure that they are completed satisfactorily and obtaining formal acceptance of deliverables by the customer or sponsor. Scope Verification differs from quality control in that scope verification is primarily concerned with acceptance of the deliverables, while quality control is primarily concerned with correctness of the deliverables and meeting the quality requirements specified for the deliverables.

Verify Scope: Inputs

Project Management Plan
Project Scope Statement - Includes the project description, Project Content and product user acceptance criteria. WBS (Work Breakdown Structure) - Defines each deliverables and the decomposition of the deliverables into work packages. WBS Dictionary - A detailed description of work and technical documentation.

 Requirements Documentation - Lists all the project, product, technical and other types of requirements that must be presented for the project and product, along with their acceptance criteria. Requirements Traceability Matrix - Acts as a guide map or bridges that connects requirements to their origin and keeps track the project life cycle. Validated Deliverables - Validated deliverables have been completed and checked for correctness by the Perform Quality Control Process.

Verify Scope: Tools and Techniques

Inspection Involves examining and verifying to determine whether work and deliverables meet the requirements and product acceptance criteria.

Verify Scope: Outputs

Accepted Deliverables - This is the deliverables that are accepted and are formally signed off and approved by the customers or sponsor. Changed Requests - This is the deliverables that are NOT accepted. It is documented along with the reason for non-acceptance.

 Project Document Updates - Documentations that may be updated as a result of Verify Scope Process. Including all documents that define the product or report status on product completion.

Control Scope

Control Scope - is the process of monitoring the status of the project and product scope and managing changes to the scope baseline. Controlling the project scope ensure all requested changes and recommended corrective or preventive actions are processed through the Perform Integrated Change Control process. Used to manage the actual changes when they occur and is integrated with the other control processes.

Control Scope: Inputs

Project Management Plan
Scope Baseline - scope baseline is compared to the actual results to determine if a change, corrective action, or preventive action was necessary. Scope Management Plan - describes how the project scope will be managed and controlled. Change Management Plan - defines the process for managing changes on the project

 Configuration Management Plan- defines those items that are configurable, those items that require formal change control, and the process for controlling changes to such items. Requirements Management Plan includes how requirements activities will be planned, tracked and reported and how changes to the product, service, or result requirements will be initiated. It also describes how impacts will be analyzed and the authorization levels required to approve these changes.

 Work Performance Information - Information about project progress, such as which deliverables have started. Their progress and which deliverables have finished. Requirements Documentation Requirements documentation describes how individual requirements meet the business need for the project. requirements may start out at a high level and become progressively more detailed as more is known

 Requirements traceability Matrix

links requirements to their origin and tracks them throughout the project cycle life.

Organizational Process Assets

The organizational process assets that can influence the Control Scope process include but are not limited to:
Existing formal and informal scope controlrelated policies, procedures, and guidelines Monitoring and reporting methods to be used

Control Scope: Tools and Techniques

Variance Analysis - Project performance measurements are used to assess the magnitude of variation from the original scope baseline. Important aspects of project scope control include determining the cause and degree of variance relative to the scope baseline and deciding whether corrective or preventive action is required.

Control Scope: Outputs

Work Performance Analysis - Measurements can include planned vs. actual technical performance or other scope performance measurements. This information is documented and communicated to stakeholders. Change Request - Change request can include preventive or corrective actions or defect repairs. Change request are processed for review and disposition according to the perform integrated change control process

 Organization Process Assets Updates

Organizational Process assets that may be updated include, but are not limited to:

Cause of Variances. Corrective action chosen and the reasons. Other types of lessons learned from project scope control.

 Project Management Plan Updates

Scope Baseline Updates - if the approved change request have an effect upon the project scope, then the scope statement, the WBS, and the WBS dictionary are revised and reissued to reflect the approved changes. Other Baseline Updates - if the approved change request have an effect on the project scope, then a corresponding cost baseline and schedule baselines are revised and reissued to reflect the approved changes.

 Project Documentation Updates

Project document that may be updated include, but are not limited to:

Requirements documentation Requirements traceability matrix