Chapter 6 - Project Scope Management Flashcards
Product Scope
FeTures and functions that characterize a product, service, or result.
Requirements for the product.
Microsoft server that will send emails, receive emails, and synchronize contacts.
Project Scope
The work that is needed to deliver a product, service, or result with specialized features and functions.
Tells you what the project is about.
Installing a Microsoft server and updating all user accounts and workstations.
Agile or Hybrid Projects
Expect the scope to change as the project evolves.
Team determines the number of iterations or sprints it will take to complete the project.
Sprint Planning
The agile team determines which features will get done in which sprint.
Release Planning
Will determine which features will be released to the customers.
Generally includes multiple sprints.
Product Roadmap
A high-level document that outlines what would be expected of the actual product.
Plan Scope Management
This process is about creating scope and requirement management plans.
These plans will document how the project will collect requirements.
Define, validate, and control the scope.
Plan Scope Management Process
Inputs: project charter, project management plan, enterprise environmental factors, organizational process assets
Tool & techniques: expert judgement, data analysis, meetings
Outputs: scope management plan, requirements management plan
Scope Management Plan
Document how you are going to write the scope statement, how you are going to baseline the scope, how you are going to control the scope, and how you will get the scope accepted (validated).
Part of the Project Management Plan.
Requirement Management Plan
Shows the requirements to be collect, analyzed, documented, and managed.
Part of the Project Management Plan.
Collect Requirements
Defining and documenting stakeholders’ needs to meet project objectives.
Interact with the stakeholders to gather the requirements that they would like to see in the project.
Important to ensure the product is successful and actually meets the needs of the stakeholders.
Collect Requirements Process
Inputs: project charter, project management plan, project documents, business documents, agreements, enterprise environmental factors, organizational assets
Tools & techniques: expert judgement, data gathering, data analysis, decision making, data representations, interpersonal and team skills, prototypes, context diagrams
Outputs: requirements documentation, requirements traceability matrix
Data Gathering
Brainstorming
Interviews
Focus groups
Questionnaires and surveys
Benchmarking
Data Representation
Idea/mind mapping: ideas are drawn instead of written
Affinity diagram: allows many ideas to be put in a group
Interpersonal and Team Skills
Nominal group technique: rank and prioritize the ideas in brainstorming
Delphi technique: requirements are collected anonymously from SME’s
Observation/conversation: observe the stakeholders and have them show you the problem / conversation is simply talking directly with people
Facilitation: facilitated workshops are interactive discussions designed to quickly define requirements, solve differences, and build trust
User stories: used for agile projects; as a (role/user type) I want (goal) so that (motivation/reason): non-technical and easily understandable by users
Prototypes
Working models of a product
Agile projects may use storyboarding: images or illustrations that are used to show a mock-up of what the program would look like. Show various input screens in the process.
Context Diagrams
Visually show how a business process, other systems, and people interact.
Use drawings to show the inputs and outputs of a system.
Requirements Documentation
Documentation of the actual requirements that are needed on the project.
Very detailed
Requirements must be measurable, testable, and acceptable to the stakeholders of the project.
Components may include: business requirements, stakeholder requirements, organizational impacts, quality requirements, legal or ethical compliance, and requirements, assumptions and constraints
Requirements Traceability Matrix
A table created to link the requirements back to their origin.
Tracks where the requirement suggestion came from, which stakeholder gave the requirement, an why it was added to the actual project.
Define Scope
Create the project scope statement.
Scope of the project is iterative — starts as high-level but later becomes detailed.
Traditional project: scope is stored in the project scope statement
Agile project: the scope or requirements are stored in the product backlog
Define Scope Process
Input: project charter, project management plan, project documents (main ones are requirements documentation and risk register), enterprise environmental factors, organizational assets
Tools & techniques: expert judgement, data analysis, decision making, interpersonal and team skills, product analysis
Output: project scope statement, project documents updates
Project Scope Statement
One of the most important documents in the planning processes.
Includes both the project and the product scope.
Describe in detail the project deliverables and the work that will be required to produce those deliverables.
Description of the product scope
Detailed list of deliverables
Acceptance criteria
Constraints
Assumptions
Create Work Breakdown Structure (WBS)
Breakdown the deliverables into smaller, more manageable components (decomposition).
The main output of this process is the scope baseline which includes the scope statement, WBS, and the WBS dictionary.
Create WBS Process
Input: project management plan, project documents (main ones are requirements documentation and the scope statement), enterprise environmental factors, organizational process assets
Tools & techniques: decomposition, expert judgement
Output: scope baseline
Scope Baseline
One of the main components of the project management plan.
Made up of:
- the project scope statement
- WBS
- WBS dictionary
WBS
The subdivided work that needs to get done to produce the project deliverables listed in the scope statement
Hierarchical in design
Control accounts that are broken down into work packages
Rolling wave plan: team may wait until the work is better understood before decomposing all the deliverables
WBS Dictionary
A document that has more details about each work package in the WBS.
Contains: the name, description, assigned to, date assigned, estimated cost, duration, due date, account code
Agile Project: Decomposing Work
The epic is decomposed into features
Features into stories
Stories into tasks
Validate Scope
Project deliverables are formally inspected and accepted by the customer or sponsor
Done at the very end of all the executing and monitoring and controlling processes
Validate Scope Process
Input: project management plan (scope baseline and scope management plan), project documents (requirements traceability matrix, requirements documentation, lessons learned register, and quality reports), verified deliverables, work performance data
Tools and techniques: inspection, decision making
Outputs: accepted deliverables, change requests, work performance information, project documents updates
Control Scope
Ensure the projects stays on scope as it is executed
Work being done is within the scope of the project
Done on a daily basis
Traditional project: any change to scope must go through “perform integrated change control process” where the change is reviewed and authorized
Agile or hybrid project: changes are added to the product backlog and prioritized by the product owner
Control Scope Process
Input: project management plan (scope baseline and scope management plan), project documents ( requirements traceability matrix, requirements documentation, lessons learned register, and quality reports), work performance data, organizational process assets
Tools and techniques: data analysis (variance analysis or trend analysis)
Outputs: work performance information, change requests, project management plan updates, project documents updates, organizational assets updates
