Project Scope Management - Chapter 5
Benchmarking
Generating ideas by comparing specific project practices or product characteristics to those of other projects or products inside or outside the performing organization; can also be used to collect requirements
- influence the factors that cause scope changes - assure changes are processed according to procedures developed as part of integrated change control - manage changes when they occur
Goals of scope control
Most difficult Project Scope Management Process
Validating - because it involves verifying the scope and minimizing scope changes
Iterative approach - because requirements are often unclear early in a project
What approach should be used in defining requirements. Why?
WBS dictionary
document that describes detailed information about each WBS item
Variance
difference between planned and actual performance
Validating scope
Formalizing acceptance of the project deliverables
- unit of work only appear in one place - work content of WBS item is the sum of the WBS items below it - WBS item is responsibility of only one individual - must be consistent with the way the work is actually going to be performed
Advice for creating WBS
Scope
All the work involved in creating the products of the project and the processes used to create them
Analogy, top-down, bottom-up, mind mapping
Approaches to developing WBS
Requirements
Conditions or capabilities that must be met by the project or present in the product, service, or result to satisfy an agreement or other formally imposed specification
Controlling scope
Controlling changes to project scope throughout the life of the project
Scope control
Controlling changes to the project scope
Collecting requirements
Defining and documenting the features and functions of the products as well as the processes used for creating them
Work Breakdown Structure (WBS)
Deliverable-oriented grouping of the work involved in a project that defines the total scope of the project; foundation document showing the basis of planning & managing schedules, costs, etc
Planning Scope
Determining how the project's scope and requirements will be managed
Requirements Management Plan
Documents how project requirements will be analyzed, documented, and managed
Customer inspection and then sign-off on key deliverables
How is validation acceptance achieved?
Scope Baseline
Includes the approved project scope statement and its associated WBS and WBS dictionary
Requirements Traceability Matrix (RTM)
Is a table that lists requirements, various attributes of each requirement, and the status of the requirements to ensure that all requirements are addressed
Vague
Many WBS tasks are ____
-Interviewing -Focus groups/facilitated workshops -Group creativity & decision making techniques -Questionnaires and surveys -Observation -Prototyping
Methods for Collecting Requirements
Scope Management Plan and Requirements Management Plan
Outputs of Planning Scope Management
Project Management Scope Processes
Planning scope, Collecting requirements, Defining scope, Creating the WBS, Validating scope, Controlling scope
Deliverable
Product produced as a part of a project, such as hardware or software, planning documents, or meeting minutes
Elicitation, analysis, specification, and validation
Requirements development categories
Analogy approach
Review WBS of similar projects and tailor to your project
Defining scope
Reviewing the project charter, requirements, documents, and organizationals process assets to create a scope statement
how to's: slide 8
Scope Management Plan Contents?
Project scope statements (PSS)
Should include at least a product scope description, product user acceptance criteria, and detailed information on all project deliverables; also helpful to document other scope-related information, such as the project boundaries, constraints, and assumptions; should also reference supporting documents, such as product specifications
Top-down approach
Start with the largest items of the project and break them down
Bottom-up approach
Start with the specific tasks and roll them up
Decomposition
Subdividing project deliverables into smaller pieces
Creating the WBS
Subdividing the major project deliverables into smaller, more manageable components
Scope management plan
Subsidiary part of the Project Management Plan
True
T/F the scope of a project becomes more clear as time progresses
Work Package
Task at the lowest level of the WBS
Mind mapping approach
Technique that uses branches radiating out from a core idea to structure thoughts and ideas
Project Scope Management
The processes involved in defining and controlling what is or is not included in a project
Expert judgement and meetings
Tools of Planning Scope Management
Scope validation
involves formal acceptance of the completed project deliverables
