IT Project Management: Planning - Scope
IT Project Management: Planning - Scope
Lecture 3
Planning – Scope
Project Management Process Groups and Knowledge Areas Map
Project Management Process Groups
Knowledge Areas
Initiating Planning Executing Monitoring & Controlling Closing
4. Project 4.1 Develop 4.2 Develop Project 4.3 Direct and Manage 4.5 Monitor and Control 4.7 Close Project
Integration Project Management Plan Project Work Project Work or Phase
Management Charter 4.4 Manage product 4.6 Perform Integrated
knowledge Change Control
5. Project Scope 5.1 Plan Scope Management 5.5 Validate Scope
Management 5.2 Collect Requirements 5.6 Control Scope
5,3 Define Scope
5.4 Create Work Breakdown
Structure (WBS)
6. Project Time 6.1 Plan Schedule Management 6.6 Control Schedule
Management 6.2 Define Activities
Project Time 6.3 Sequence Activities
Management 6.4 Estimate Activity Durations
6.5 Develop Schedule
9. Project 9.1 Plan Resource Management 9.2 Acquire Resources 9.5 Control Resources
Resource 9.3 Develop Team
Management 9.4 Manage Team
10. Project 10.1 Plan Communications 10.2 Manage 10.3 Monitor Communication
Communications Management Communications
Management
11. Project Risk 11.1 Plan Risk Management 11.6 Manage Risk Response 11.7 Monitor Risk
Management 11.2 Identify Risk
11.3 Perform Qualitative Risk
Analysis
11.4 Perform Quantitative Risk
Analysis
11.5 Plan Risk Response
12. Project 12.1 Plan Procurement 12.2 Manage 12.3 Conduct Procurements
Procurement Management Procurements
Management
13. Project 13.1 Identify 13.2 Plan Stakeholder 13.3 Manage Stakeholder 13.4 Monitor Stakeholder
Stakeholder Stakeholders Engagement Engagement Engagement
Management
Learning Outcomes
Explain the need for a scope management plan.
Collect requirements
Define Scope
Create WBS
Project Scope Definition
Product Scope: The sum of the features that
make up the product or service created by the
project.
TIME COST
SCOPE
Scope Statement –Components
Project scope description – characteristics of the product,
service or result
Graphical
Outline
Graphical Format Example
Outline Format Example
1.0 Concept
1.1 Evaluate current systems
1.2 Define Requirements
1.2.1 Define user requirements
1.2.2 Define content requirements
1.2.3 Define system requirements
1.2.4 Define server owner requirements
1.3 Define specific functionality
1.4 Define risks and risk management approach
1.5 Develop project plan
1.6 Brief Web development team
2.0 Web Site Design
3.0 Web Site Development
4.0 Roll Out
5.0 Support
Intranet WBS and Gantt Chart in
Microsoft Project
WBS Dictionary
“The WBS dictionary is a document that provides detailed
deliverable, activity, and scheduling information about each
component in the WBS. The WBS dictionary is a document
that supports the WBS.”
May include but not limited to:
WBS code
WBS element
Description of work
Assumptions and constraints
Resources required
Cost estimates
Acceptance criteria
PMBOK Guide Sixth Edition
WBS Example – Format #1
WBS WBS WBS Name WBS Description
Level Code
1 1 Web Site Design Creation of a document that provides details of the web site
design including overall look and feel and a template for the
layout of web pages on the site
2 1.1 Site Map A page showing
2 1.2 Graphic Design Layout of pages on the web site including all graphic
elements.
2 1.3 Programs Details specification of JavaScript programs used.
1 2 Home Page Details of all elements on the home page
2 2.1 Text Text included in the home page
2 2.2 Images Images to be displayed on the home page
2 2.3 Hyperlinks Hyperlinks description and the pages they are linked to
2 3 Marketing Page Details of all elements on the home page
WBS Example – Format #2
Intranet Project
WBS WBS Element
Code
[WBS [WBS element name]
code]
WBS Element Description
[include a brief definition of the WBS element (function, deliverable, etc.) associated
activities, milestones, and other information such as performance measurement
criteria, statement of work paragraph number, contract line item, start and end dates,
resource requirements, cost estimates, quality requirements, technical content,
contact information, revision history, etc.]