Project Integration

Management

&

Project Scope
Management
Project Integration Management-Processes

Integration is primarily concerned with effectively integrating the processes among

the Project Management Process Groups that are required to accomplish project
objectives within an organization’s defined procedures. It has following processes:

• Develop Project Charter

• Develop Project Management Plan
• Direct and Manage Project Work
• Manage Project Knowledge
• Monitor and Control Project Work
• Perform Integrated Change Control
• Close Project or Phase
Sample Project Charter

The project charter

typically documents the
following parts of the
project:
• Project objectives
and constraints
• Timelines
• Key stakeholders
• Risks identified
• Benefits of the
project
• General overview
of the budget
Project Scope-Processes

Project Scope Management includes the processes required to ensure that the - project
includes all the work required, and only the work required, to complete the project successfully.
It is primarily concerned with defining and controlling what is or is not included in the project. It
has following processes:

1. Scope planning: deciding how the scope will be defined, verified, and controlled
2. Scope definition: reviewing the project charter and preliminary scope statement and
adding more information as requirements are developed and change requests are approved
3. Creating the WBS: subdividing the major project deliverables into smaller, more
manageable components
4. Scope verification: formalizing acceptance of the project scope by key project stakeholders
5. Scope control: controlling changes to project scope which impact project cost and time
goals
 Creating
Work Breakdown Structure
(WBS)

Just tell me
what I have
to do!
 Create WBS
 A WBS is a deliverable-oriented grouping of the work involved in a project that defines the total
scope of the project

 WBS is a foundation document that provides the basis for planning and managing project
schedules, costs, resources, and changes

A work breakdown structure (WBS) is a tool used to graphically display the deliverables of the
project in a hierarchical fashion. It organizes the work of the project into logical groupings and
displays the information in a tree form or an outline form.

A deliverable-oriented hierarchy that defines all the work of the project. Each succeeding level
has more detail than the level above it.

The work package level is the lowest level in the WBS, and is the point at which the cost
and schedule for the work can be reliably estimated. The level of detail for work packages will vary
with the size and complexity of the project.
 Create WBS

It is common to have four to six levels in designing WBS.

WBS (the highest level) may include deliverables, milestones, or process groups or subprojects
within the project, depending on:

How the WBS is structured

How large and complex is the project

The entire project team should be involved in developing the work breakdown structure. When
completed, it should be reviewed with the customers as well.
 Create WBS

Identification Codes:
Identifiers or WBS codes, allow you to uniquely identify each element of WBS. This information is used to track
the cost of the work or may also serve as the reference number to other planning information, e.g., start date,
end date, resources etc..

Some project managers include enough detail so that WBS can be used as an instrument for
scheduling, personnel assignment, resource allocation, monitoring project progress and controlling
how and when tasks are accomplished.

 WBS is the foundation for all the future work. After work has actually begun it is really frustrating
to discover that an essential task has not been considered. Re-planning a project again and again is
both difficult and expensive.
 Why use WBS ?

• To document all work that must be done to develop &

deliver the system in a satisfactory manner

WBS
WBS
 Is WBS necessary?

• WBS serves to consolidate information from many sources

into one place and into an organized format.

A
A “table
“table of
of contents”
contents” for
for the
the project.
project.
Sample Work Breakdown Structure with Some Branches Decomposed
Down Through Work Packages

11
 Create WBS
What’s important in creating WBS
 You get the WBS to a point where the components in the lowest level of the hierarchy
are easily estimated, scheduled and assigned.

 The idea is to keep adding levels to the WBS until you have broken the work out to
the point where responsibility for each unit of work can be assigned to a specific
person or to a team.
 Create WBS
Sample Intranet WBS Organized by Product

13
 Create WBS
Intranet WBS in Tabular Form (Outline View)
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
14

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
 Create WBS
Intranet WBS and Gantt Chart in MS Project

15
 Create WBS
Sample Intranet WBS Organized by Phase

16
 Approaches to developing WBS

• Analogy approach: Review WBSs of similar projects and tailor to your project.

• 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.

• Mind-mapping approach: Write tasks in a non-linear, branching format and then create the WBS
structure.
 Create WBS
Sample Mind-Mapping Approach

18
 Create WBS
Resulting WBS in Chart Form

19
 Example 1

Let’s do an example now to “Serving the breakfast in a Room”

1.WBS
2.WBS as Outline View
 100% Rule

The next level decomposition of

a WBS element (child level)
must represent 100% of the
work applicable to the next
higher (parent) element.
 WBS (Work Breakdown Structure)

Serve breakfast in a Room

Produce glass Produce boiled Produce Arrange

of orange juice egg in egg cup butter toast tray

Obtain Obtain Produce Obtain Produce Obtain

22
Produce Obtain Plates &
glass juice Boiled egg egg cup toast butter tray
cutlery

Obtain egg Obtain water Obtain bread

 Rolling-up Costs

$301K

$112K $85K $28K $45K $31K

$22K $13K $15K $38K $24K

 Example 2
Let’s do an example now to construct WBS, it’s Outline View, Activity/Task List and
Milestone Chart or Milestone Chart.

You have been assigned as the project manager for your company’s upcoming
annual conference. Customers from all over the world fly to your city to attend this
conference and learn about your company’s products, take some training classes
And meet with vendors. Or Plan a Holiday Trip!
Develop:

1.WBS
2.WBS as Outline View
 WBS
Annual Conference Project

10.0 20.0 30.0

PCs Set up Brochures mailed Training Prepared

20.1 20.2 30.1 30.2

10.1 10.2
Prepare Mail Prepare Prepare
Obtain PCs Set up PCs
Brochures
25
Brochures Content media

10.1.1 10.2.1 20.1.1 20.2.1

Sign lease Install Design Prepare 30.1.1 30.2.1
agreement Power Strips Brochures mailing list Write Print
Content materials
20.1.2 20.2.2
10.1.2 10.2.2 Print Affix 30.1.2 30.2.2
Arrange Load Brochures labels Review Prepare
Delivery Software content notebooks
 Assignment #2
Develop WBS for your semester projects (for which you made proposal as
Assignment#1)

Develop:
1.WBS (block diagram or tree form as we have done in class)
2.WBS (the same) in MS Project or any other software

Due Date: (11th March for Section-A)

(13th March for Section-B)
Discussion / Questions
?