Project Scope Management Flashcards
Predictive
Scoped defined at beginning
Change resistant
Adaptive
Project scope developed throughout iterations
Expect changes
Product Scope
Features or functions
Does not tell you what the project is about, just tells you what it can do
Characteristics of what customers expect, their deliverables.
Productive backlog in adaptive
Product Backlog
Big list of all requirements
Prioritized
Scope
What the project will actually accomplish
Includes ONLY the work required
Project Scope
Work needed to deliver a product, service, or result.
Actually tells you what the project is about
Plan Scope Management PROCESS
In Planning Process Group
Main Output Creating Scope Management Plan and Requirement Management Plans
PM documents next steps needed to do the next 5 processes in this area
Project Management plan is an input
Collect Requirements PROCESS
In Planning Process Group
Defining and documenting stakeholders needs to meet project objectives
Main Output= Requirements Documentation and Requirement Traceability Matrix
Define Scope PROCESS
In Planning Process group
Main output= Create project scope statement
Scope is iterative- May take time to determine actual scope
In a Traditional project, scope is stored in project scope statements
In a Agile Project, scope is stored in product backlog
Create Work Breakdown Structure PROCESS
In Planning Process Group
Breaking down deliverables into smaller more manageable components–
Main output is scope baseline
WBS is hierarchical , top level is general, lower level is detailed
Control accounts are broken down into work packages
Validate Scope PROCESS
In Monitoring and Controlling Process group
Main Output= Accepted deliverables and Work Performance Information
Project deliverables are formally inspected and accepted by the customer or sponsor
Done at the end of a project
Control Scope PROCESS
In Monitoring and Controlling Process group
Main output= Change Request and Work Performance Information
Goal is to ensure project stays on scope as it is executed
Make sure the work the project team is doing is actually in the scope
done on a daily basis
Product Road Map
Agile
High level document that outlines what would be expected of the actual project
Outlines all of the releases
Benchmarking
Looking at industry best practices for how fast a website should load
Idea Mapping
Way to represent data
Ideas are drawn instead of written
Joint Application Development JAD
Subject matter experts and developers meet to improve the software development process
Prototypes
Working models of a product that stakeholders can interact with.
Agile uses prototypes
Storyboarding
Prototyping technique used on agile projects
it is a series of images that are used to show a mockup of what the program would look like once a user is using it.
Facilitation
Bring together stakeholders to gather requirements
EX workshop
Obeservation
Viewing stakeholders in their work enviroment
User Stories
As a <role/user type>, I want <goal> so that <motivation/reason></goal>
Requirements Traceability Matrix
Table created to link requirements back to their origin.
Project Scope Statement
Includes:
Description of scope
Acceptance Criteria
Exclusions
Constraints
Assumptions
Explains project deliverables and work required to complete the deliverables
Risk Register
Shows risks that can impact the scope
Decomposition
Take project deliverables from scope statement and divide them into smaller parts, known as work packages (Lowest level on WBS used to estimate time and cost)
Scope Baseline
Made up of three components
-Project scope statement
-WBS
-WBS Dictionary
WBS Dictionary
document that has more details about each work package
Epics
How work is decomposed on an agile project
large initiatives to deliver new products or solutions to customers.
Epics are decomposed into features
Features are decomposed into stories
and task are the the decomposition of user stories
Control Quality
Process where deliverable is inspected to see if it meets the quality requirements
Do this before you take to a customer or sponsor for formal acceptance
Variance Analysis
Determines if there is a variance between the planned work (PM Plan) and the actual work (Work performance data)
Work Performance Information
States if project is in scope or not
Completion of Project scope is Measured against?
Project Management Plan
Project Scope Statement
The WBS
WBS Dictionary
Code of Accounts
Formal name for numbering system found in WBS
it allows the following:
-Link the work packages to specific account codes used to track project costs
-Helps project manager identify level at which work package is found
