GL8 e Chap 04 S
GL8 e Chap 04 S
4–2
Defining the Project
4–3
Step 1: Defining the Project Scope
• Project Scope
– A definition of the end result or mission of the
project—a product or service for the
client/customer—in specific, tangible, and
measurable terms.
• Purpose of the Scope Statement
– To clearly define the deliverable(s) for the end user.
– To focus the project on successful completion
of its goals.
– To be used by the project owner and participants
as a planning tool and for measuring project success.
4–4
Project Scope: Terms and Definitions
• Scope Statements
– Also called statements of work (SOW)
• Project Charter
– Can contain an expanded version of scope statement
– A document authorizing the project manager to
initiate and lead the project.
• Scope Creep
– The tendency for the project scope to expand over
time due to changing requirements, specifications,
and priorities.
4–5
Step 2: Establishing Project Priorities
• Causes of Project Trade-offs
– Shifts in the relative importance of criterions related
to cost, time, and performance parameters
• Budget–Cost
• Schedule–Time
• Performance–Scope
4–6
Step 3: Creating the Work
Breakdown Structure
4–7
How WBS Helps the Project Manager
• WBS
– Facilitates evaluation of cost, time, and technical
performance of the organization on a project.
– Provides management with information appropriate
to each organizational level.
– Helps in the development of the organization
breakdown structure (OBS). which assigns project
responsibilities to organizational units and individuals
– Helps manage plan, schedule, and budget.
– Defines communication channels and assists
in coordinating the various project elements.
4–8
Work Packages
• A work package is the lowest level of the WBS.
– It is output-oriented in that it:
1. Defines work (what).
2. Identifies time to complete a work package (how long).
3. Identifies a time-phased budget to complete
a work package (cost).
4. Identifies resources needed to complete
a work package (how much).
5. Identifies a person responsible for units of work (who).
6. Identifies monitoring points (milestones)
for measuring success.
4–9
Step 4: Integrating the WBS
with the Organization
4–10
Step 5: Coding the WBS for
the Information System
4–11
Responsibility Matrices
• Responsibility Matrix (RM)
– Also called a linear responsibility chart.
– Summarizes the tasks to be accomplished and
who is responsible for what on the project.
• Lists project activities and participants.
• Clarifies critical interfaces between units
and individuals that need coordination.
• Provide an means for all participants to view their
responsibilities and agree on their assignments.
• Clarifies the extent or type of authority that
can be exercised by each participant.
4–12
Project Communication Plan
4–13
Information Needs
4–14
Key Terms
Cost account
Milestone
Organization breakdown structure (OBS)
Priority matrix
Process breakdown structure (PBS)
Project charter
Responsibility matrix
Scope creep
Scope statement
WBS dictionary
Work breakdown structure (WBS)
Work package
4–15