Samenvatting Project Management Advanced

1. Project initiation
o First phase = start project
o Business case:
 Detailed description problem/opportunity
- Introduction, business objectives, problem/opp statement,
assumptions, limitations
 Alternative solutions
 Analysis of business benefits, costs, risks, issues
 Description preferred solution
 Project requirements
 Summarized plan --> schedule + financial analysis
o Project sponsor approves business case + required funding is allocated
--> proceed feasibility study --> PS determine if it’s worth it/ profitable
o Completion + approval feasibility study = start planning phase
o Success of project
 Depends on clarity + accuracy business case
 Interpreted in multiple ways = lacks clarity
 Best way to make objective clear = state it so it can be verified

2. The project charter
o Purpose:
 Provides understanding, reason, justification of project
 Establish general scope
 Establish project manager + his authority
 Includes who reviews + approves project charter
o Includes:
 An identification section
 The overview of the project
 The objective
 The scope
 Major milestones
 Major deliverables
 Assumptions
 Constraints
 Business need or opportunity
 Preliminary cost
 Project risks
 Project charter acceptance
 Project stakeholders

3. project planning phase
o Purpose:
 Establish business requirements
 Establish cost, schedule, deliverables, delivery dates
 Establish resources plans
 Obtain management approval

, o Basic processes
 Scope planning
 Preparation WBS
 Project schedule development
 Recourse planning
 Budget planning
 Purchase planning
 Risk management
 Quality planning
 Communication planning
o Project requirements
 Requirements describe characteristics of final deliverable
 Specific requirements the final deliverable must have to satisfy
objectives of project
 Six categories:
- Functional = WHAT deliverable must do
- Non-functional = specify criteria -> performance, development
(time, resource, quality)
- Technical = HOW it needs to be designed
- Business = The needs of the sponsoring organization, from a
management perspective.
- User = what user needs to do with it
- Regulatory = Can be internal or external, are usually non-
negotiable: restrictions, licenses, laws
o Scope inputs
 ->




o WBS
 ->




4. The scope statement
o Details project deliverables + describes major objectives
o Objectives should include measurable success criteria
o Contain
 Project name
 Project charter
 Owner, sponsors, stakeholders
 Problem statement
 Project goals + objectives
 Project requirements
 Project deliverables

,  Non-goals
 Milestones
 Cost estimates

5. Project schedule planning
o Defining activities
 Further breakdown of work package elements of WBS
 Individual units of work --> complete to fulfill deliverables
 Uses everything we know about project to divide work into activities
that can be estimated
o Activity list
 Everything that needs to be done to complete project
 Including all activities that must be accomplished to deliver each
work package
 Kinds of predecessors:
- Finish-to-start: first activity needs to be finished before next
one can start
- Start-to-finish: first an activity needs to start before the activity
can finish
- Finish-to-finish: both activities need to end together.
- Start-to-start: both activities need to begin at the same
moment.
- External predecessors: depends on things outside your project
- Discretionary predecessors: if you want
- Mandatory predecessors: have to exist because of the nature
of the work
 Leads/ Lags
- Lag time = put a delay
- Lead time = give successor task some time to get started
before predecessor finishes
o Milestones
 Important checkpoints
 Some can be contracted -> requirement of successful completion
 Some can be significant points -> keep track of
 Milestone list -> let know which are required an which not
o Network diagram
 ->



o Gantt chart
 ->