Scope Management

Project Scope Management (PMP)

Project Scope Management

6 processes

1. Plan Scope Management (P) - Scope Mgmt Plan Reqs Mgmt Plam

2. Collect Requirements (P) - Reqs docs, Reqs Traceability Matrix

3. Define Scope (P) - Project Scope Statement

4. Create WBS (P) - Scope Baseline, WBS, WBS Dictionary

5. Validate Scope (MC) - Accepted Deliverables

6. Control Scope (MC) - Change Requests, Work Performance Info

Product Scope Vs Project Scope

• Product Scope:

  • Features and functions that characterizes a product, service or result

  • Requirements for the product

  • Tells what the product can do

• Project Scope:

  • Work is needed to deliver the product, service, or result with specified features and functions.

  • Clarifies what project is trying to accomplish

  • Agile project: expect the project scope to change as the project evolves

    Two types of planning- Sprint Planning and Release Planning

]

Plan Scope Management

• This process is about creating

  • Scope and

  • Requirements Management Plan

• Documents- how the requirements will be collected, and how the scope will be defined, validated, and controlled.

• Inputs -

  1. Project Charter

  2. Project Management Plan

  3. EEF

  4. OPA

• TT:

  1. Expert Judgement

  2. Data Analysis

  3. Meetings

     Outputs

     1. Scope Mgmt Plan

     2. Requirements Mgmt Plan

Scope Mgmt Plan

• Includes:

  • Scope statement

  • Scope Baseline

  • How to validate and control the scope

• In Predcitive Projects -

  • State the requirements by describing objectives, deliverables, boundaries, and acceptance criteria.

Requirements Mgmt Plan

Shows how the requirements will be collected, analyzed, documented, and managed.

Collect Requirements

• This process group -

  • Defining and documenting stakeholders’ needs to meet the project objectives.

  • Interact with the stakeholders to gather the requirements

    • Start with the MVP stakeholders.

    • Gather from all

• In traditional = it’s collected during the planning phase, then no more reqs gathering during the execution

  In Agile = it could be given during the entire duration of the project. Customer may add more when they see the smaller increments

• Inputs:

  • Project Charter

  • PM Plan

  • Project Docs

  • Business Docs

  • Agreeements

  • EEF

  • OPA

• TT -

  • Expert Judgement

  • Data Gathering - Brainstorming, Interview, Focus Group, Questionnaire, Survey, Benchmarking

  • Data Analysis

  • Decision Making

  • Data Representation - Idea/Mind Mapping, Affinity Diagram

  • Interpersonal and Team Skills - Nominal Group, Delphi, Observations/Job Shadowing, Facilitations, User Stories

  • Prototypes

  • Context Diagrams

• Outputs

  • Requirements Documentation

  • Requirements Traceability Matrix

Idea Mind Mapping

Ideas are drawn rather than written

Affinity Diagram (groups)

Ideas are put together in groups or

Group notes into clusters and find patterns

Nominal Group Technique (TT- under Team skill)

Rank and prioritize ideas in brainstorming

Delphi Technique (TT under Team skills)

Collect the reqs anonymously

Not to influence others opinion

Joint Application Development (JAD)

• Facilitation/ Observation Eg. JAD

• SME and Developers work together to improve the software deve processes

User Stories

• Description of required functionality

• Adds value for the user

• Short and simple

• Usually in the form of Story Card - Outline as: As a user > I want (goal) > so that <motivation/reason)>

  • Story card also contains - acceptance criteria and how it will be tested

• Non technical, easy to understand

• Clearly defined

• Smallest unit of work

• INVEST

  • Independent

  • Negotiable

  • Valuable

  • Estimate

  • Small

  • Testable

Context Diagram

Visually shows how a business process, other systems, and people interact.

Requirements Documentation

• Actual requirements documents

• Very detailed

• Can be high level at the beginning, but can be elaborated during the execution

• Requirements should be - measurable, testable, and acceptable to stakeholders

Requirements Traceability Matrix

Table created to link the reqs back to their origin (where the suggestion/req came from)

Define Scope (P)

• Create Scope Statement

• Understand and analyze the reqs from the reqs documentation

• Select the final req to become the final product, service, or results of the project.

• Once the scope is baselined during the Create WBS process, you will need a change request to make any changes.

• Agile - due to uncertainty, early phase, it could be high level

• Scope of the project is iterative.

• Discuss with the selective stakeholders before finalizing to make sure that all of their reqs are captured.

• Scope of the project

  • TraditionalPr project = lies in the scope statement

  • Agile = lies in the product backlog

Project Scope Statement

• Description of the product scope

• Dedicated deliverables

• Acceptance criteria

• Exclusions

• Assumptions

• Constraints

Create WBS

• Process of breaking down deliverables into smaller, more manageable components,

• Main output - Scope Baseline

  • Includes - scope statement, WBC, and WBC Dictionary

• Scope Statement is broken down

• Detail the work, that is needed to complete the project deliverable.

Decomposition (TT)

• Technique where deliverables from the scope statement broken into smaller parts, i.e., work packages.

• Works packages = lowest level of the WBS

• Estimate - cost, time, and resource mgmt

• If too high level, estimates may not be accurate

WBS

• Hierarchical decomposition of the deliverables

• More detail

• Provides a structure for the summation of the cost, schedule, and resource info.

WBS Dictionary

• Has more details about each work packages in the WBS

• Detailed description of cost estimates, scheduling, assumptions, constraints, and acceptance criteria

Validate Scope

• Formally inspected and accepted by the customer or sponsor

• Main output = accepted deliverables

• This is done after, control quality, or both processes be done at the same time.

• Control quality to ensure that the deliverables are correct and needs to be checked before accepted.

• Main TT - Inspection (measure, examine, and validate.

Control Scope

Make sure the project stays on the scope as it’s executed.