Scope Management. Chapter 5. Learning Goals . Understand the importance of scope management for project success. Construct a Work Breakdown Structure for a project. Develop a Responsibility Assignment Matrix for a project.
Project scope is everything about a project – work content as well as expected outcomes, which should include
- activities to be performed
- resources consumed
- end product result
- quality standard expected
Scope management is the function of controlling a project in terms of its goals and objectives and consists of:
1) Conceptual development 4) Scope reporting
2) Scope statement 5) Control systems
3) Work authorization 6) Project closeout
See Table 5.1 for details
The process that addresses project objectives by finding the best ways to meet them.
Collect data and develop information:
Sets the stage for the project
Successful conceptual development requires:
A SOW is a detailed narrative description of the work required for a project.
Effective SOWs contain
See UPMM_IIL_Project Charter.docand Table 5.2
A process that sets a project’s scope by breaking down its overall mission into a cohesive set of synchronous, increasingly specific tasks.
What does the WBS accomplish?
Lowest level in WBS
Organizational Breakdown Structure (OBS) allows
OBS links cost, activity & responsibility
Match IT to
1.3Responsibility Assignment Matrix
See UPMM_IIL_Responsibility Assignment Matrix (RAM).doc
Let the work begin!!
The formal “go ahead” to begin working the project.
Follows the approval of scope management steps:
Most contracts contain:
Contracts range from:
Determines what types of information is reported, whoreceives copies, when, and how information is acquired and disseminated.
Typical project reports contain
Solid communication between all parties is one of the most important task to be accomplished.
Poor Scope Statements!
Control systems are vital to ensure that any changes to the project baseline are conducted in a systematic and thorough manner.
How does a project become a year late? One day at a time!
See UPMM_IIL_Project Change Request Form.doc
The job is not over until the paperwork is done…
Closeout documentation is used to:
Train project managers
Closeout documentation includes:
Post project analysis – post-mortem process
ImaPrez says, “I want a phone system like the company downstairs.”