Scope Management - Quick Reference Card
Roadmap stages
Opportunity
Evaluation
Scope Management Processes for Projects
Development & Bid
Negotiation & Close
Delivery
SOAR Event
Opportunity Assessment Approval
Bid Approval
Ts & Cs Approval
Scope Change Approval
Activities
Establish Project Business Need
and Solution Description
Assign Project Manager
Develop Scope Statement & WBS
Update Scope Statement with
Details
Review Requirements and
Proposed Solution
Validate Scope with Client
Manage Scope Delivery and
Scope Changes
Obtain Acceptance
Develop Scope Statement
Define Summary-level Deliverables
Define Acceptance and Quality
Criteria
Validate Scope with Client
Establish Scope Change
Management Procedures
Updated Scope Statement
Updated Change Request & Log
Acceptance of Proposed Changes
Outputs
Updates to Related Documents, as
applicable, Project Plan, Schedule,
Contract, Supporting Plans, etc.
Project Charter
Scope Statement & WBS
Updated Scope Statement
Project Manager Assigned
Scope Management Plan
Change Requests
Scope Planning Worksheet
Change Request Template
Change Request Template
WBS Technique
Solution Support Template
Customer Req’ts Log
Operational Support Plan
Template
Acceptance Specification
Template
Tools
Project Initiation Worksheet
Deliverable Acceptance Template
Scope Management - Quick Reference Card
Overview of Scope Management for Projects
SCOPE MANAGEMENT
Scope management for projects involves the processes needed to ensure that
the project includes all work required, and only the work required, to complete
the project successfully. A key output of Scope Planning, and the foundation
for many follow-on planning and execution activities, is the scope statement
which documents the project justification, deliverables, and objectives.
Example of a Good Scope Statement
WHY
Client needs new XYZ system to improve customer satisfaction.
WHO
Company will deliver... and Client will...
WHEN
Company will start implementation X days after receipt of a formal
purchase order and estimate completion in X months from agreed
start date for
Y system and training.
SCOPE
MANAGEMENT
PROCESSES
1.
Initiation
2.
Planning Scope
3.
Define Scope
4.
Verify Scope
5.
Scope Change
Control
WHAT X software for Company UNIX to handle Y number of end clients as defined in
specification document ABCD and documentation as defined in plan EFGH.
Installation on Z number of machines at test site, as agreed. Rollout excluded, but may
be negotiated separately. Warranted for X number of years. Support included for Y
number of years after acceptance. Ongoing support not included or required.
Example of a Good Scope Statement
HOW Company will develop software using an internal project team including external
contractors and X number of representatives from the Client. Software will be
developed, tested, documented and accepted on Company premises with final
acceptance on the Client site, according to plan JKLM.
GUIDE
Scope Management Guide