CIS 4603 Project Management

Project Scope Management

Scope statement, WBS, WBS Dictionary and Scope Baseline

NOTES
PROJECT SCOPE STATEMENT

The project scope statement details the project’s deliverables and the work necessary to create these
deliverables. The Project Scope Statement should contain the following components:

 Product Scope Description – describes what the project will accomplish

 Product Acceptance Criteria – describes what requirements must be met in order for the project
to be accepted as complete
 Project Deliverables – detailed list of deliverables the project will result in
 Project Exclusions – description of work that is not included in the project and outside of the
scope
 Project Constraints – lists limits on resources for time, money, manpower, or equipment
(capital)
 Project Assumptions – describes the list of assumptions the project team and stakeholders are
working under to complete the project

WORK BREAKDOWN STRUCTURE

The Work Breakdown Structure (WBS) and Work Breakdown Structure Dictionary are key elements to
effective scope management. The WBS shows how project scope is to be subdivided into smaller
deliverables. The second level of the WBS can be project phases, process groups or major deliverables.
WBS Dictionary and how these smaller components are managed during the life of the project

WORK BREAKDOWN DICTIONARY

The WBS Dictionary includes an entry for each WBS element OR a work package as decided in the Scope
Management Plan. The WBS Dictionary includes a detailed description of work for each element and
the deliverables, budget and resource needs for that element. The project team will use the WBS
Dictionary as a statement of work for each WBS element.

SCOPE BASELINE:

The approved version of

 a scope statement, work breakdown structure (WBS), WBS dictionary

Scope baseline can be changed only through formal control procedures and is used as a basis for
comparison when executing the project

Page 1 of 4
SS/622320570.docx
 CIS 4603 Project Management

CASE DESCRIPTION:

This project includes the design, programming, and testing of a new software application for tracking the
company’s finances. The deliverables for this project are a completed software application for finance
tracking with the flexibility to modify and expand the application as necessary in the future.

This project will be accepted once the new software has been successfully tested by the finance
department and has been shown to be compatible with the company’s current information technology
(IT) infrastructure.

This project does not include ongoing operations and maintenance of the software. Only internal
personnel and resources may be used for this project. Additionally, the project is not to exceed 180
days in duration or $450,000 in spending. Assumptions for this project are that support will be provided
by the project sponsor and all department managers and that adequate internal resources are available
for the successful completion of this project.

Task:

Answer the following questions:

1. What project management documents are required as inputs to create the project scope
statement? What project process creates the project scope statement?
2. What must the scope statement include?
3. Write a scope statement for the above case.
4. What is the process that creates the Scope Baseline? What are the techniques necessary to
create the scope baseline
5. Create a WBS using the linear format. Write the project title, level 2 tasks and some level 3
tasks/work packages. Level 2 tasks are Project Process Groups. Level 3 tasks are deliverables.
Refer to the template in Appendix 1
6. Create a WBS Dictionary for 5 packages using the tabular format. Refer to Appendix 2.
7. Create a detailed WBS Dictionary for ONE work package using the template given in Appendix 3.

If you can do this you are all set for Quiz 2 and part 2 of the project 

Page 2 of 4
SS/622320570.docx
 CIS 4603 Project Management
Appendix 1
Sample WBS template for a typical IT project. Modify this to suit your business case and project. You
need to add some Level 4 tasks in the execution phase
Level WBS Code
1 1
2 1.1
3 1.1.1
3 1.1.2
3 1.1.3
3 1.1.4
3 1.1.5
2 1.2
3 1.2.1
3 1.2.2
3 1.2.3
3 1.2.4
3 1.2.5
3 1.2.6
2 1.3
3 1.3.1
3 1.3.2
3 1.3.3
3 1.3.4
3 1.3.5
3 1.3.6
3 1.3.7
3 1.3.8
3 1.3.9
2 1.4
3 1.4.1
3 1.4.2
3 1.4.3
3 1.4.4
2 1.5
3 1.5.1
3 1.5.2
3 1.5.3
3 1.5.4
3 1.5.5
Page 3 of 4
SS/622320570.docx
Task Title
Project Title
Initiation
Evaluation & Recommendations
Develop Project Charter
Milestone: Submit Project Charter
Project Sponsor Reviews Project Charter
Milestone: Project Charter Signed/Approved
Planning
Create Preliminary Scope Statement
Determine Project Team
Project Team Kickoff Meeting
Develop Project Plan
Submit Project Plan
Milestone: Project Plan Approval
Execution
Project Kickoff Meeting
Verify & Validate User Requirements
Design System
Procure Hardware/Software
Install Development System
Testing Phase
Install Live System
User Training
Go Live
Control
Project Management
Project Status Meetings
Risk Management
Update Project Management Plan
Closeout
Evaluate system
Document Lessons Learned
Update Files/Records
Gain Formal Acceptance
Archive Files/Documents
 CIS 4603 Project Management

Appendix 2

Level WBS Code WBS Package WBS Package Deliverable Budget Resources
Name Description

Appendix 3

WORK BREAKDOWN STRUCTURE DICTIONARY

PROJECT TITLE:

WBS CODE: (As defined in MS Project)

WBS PACKAGE NAME:

TASK DESCRIPTION (WHAT WORK IS AUTHORIZED)

ACCEPTANCE CRITERIA

DELIVERABLE(S) – What is produced

RESOURCES ASSIGNED – People, Equipment and other expenses

DURATION in Days
Optimistic –
Most likely -
Pessimistic -

COST - Approximate
DEPENDENCIES AFTER (SUCCESSOR) DEPENDENCIES BEFORE (PREDECESSOR)
DUE DATE APPROVED: PROJECT MANAGER

Page 4 of 4
SS/622320570.docx