Section 5: Project Scope Management Flashcards
Product Scope
- features and functions from the customer requirements
- characteristics of customers’ deliverable
- product scope is derived from Collect Requirements
- Validate Scope is how Product Scope Confirmation is completed
Project Scope
-work to be completed to satisfy the product scope
Includes
- project scope description
- project deliverables
- acceptance criteria
- project exclusions
Scope in Project Life Cycles
Predictive - scope defined at beginning & change resistant
Adaptive - scope developed through iterations & except changes
Scope and Project Completion
- Project Scope is measured against project plan
- Product scope is measured against project requirements
Requirements
-conditions or capabilities that must exist in a product, service or result
Project Manager and Business Analyst Relationship
- collaborative relationship
- BA has requirements responsibilities
- PM has project delivery responsibilities
- both need to say in their “swim lanes”
Inverted Triangle Model
Triple Constraints of Project Management
What is Fixed vs. Variable
- Predictive - Scope is FIXED, Time & Cost can VARY
- Adaptive/Agile - Time & Cost are FIXED, Scope can VARY
Scope Management Plan
- DOES NOT DEFINE PROJECT SCOPE
- Defines how
- ** to create project scope statement
- ** to create WBS
- ** scope baseline will be approved and maintained
- ** formal acceptance of deliverables will happen
Requirements Management Plan
- how will requirement activities be
- *planned
- tracked
- reported
- define configuration management activities(features and functions)
- define requirements prioritization process
- outline metrics to be used (Requirements traceability matrix or RTM)
Requirements traceability matrix
- a table of all the requirements
- tracks where requirements currently are in each phase
Collecting Project Requirements
- collaborate with Business Analyst
- determine, document and manage requirements
- Requirements help define the PRODUCT scope and project scope
- Collection Requirements can be performed once or at a predefined point
User Story
-make up the product backlog (list of requirements in agile)
-defines the Role, the Goal and the Motivation
Role = who benefits from feature
Goal = what is trying to be accomplished
Motivation = benefit to stakeholder (end result)
Types of Requirements
Business Requirements - higher-level needs of the organization
Stakeholder Requirements - needs of a stakeholder or stakeholder group
Solution Requirements - features, functions and characteristics of the product or service
1 - Functional requirements = describe behaviour of product
2 - Nonfunctional requirements = describe environmental conditions/qualities
Transition Requirements - from the current state to the future state
Project Requirements - actions, processes, or other conditions (forms, templates, etc.)
Quality Requirements - validate the successful completion of a project deliverable or fulfillment
Project Charter Vs Project Scope
Project Scope is about DELIVERY
Project Charter is about AUTHORITY
Work Breakdown Structure (WBS)
- WBS is a decomposition of the project scope
- subdivide the project work
- smallest item is WORK PACKAGE
- major component of the SCOPE BASELINE
