2.1_PROJECT MANAGEMENT PLAN 2020-01 (1)
docx
keyboard_arrow_up
School
Multimedia University of Kenya *
*We aren’t endorsed by this school
Course
MISC
Subject
Information Systems
Date
Nov 24, 2024
Type
docx
Pages
4
Uploaded by MasterGazelle3536
PROJECT MANAGEMENT PLAN
Project Title: Eglinton Crosstown Light Rail Transit (LRT)
Date Prepared:
Project Life Cycle:
Initiation, Planning, Execution, Monitoring & Controlling, closing
Phase
Key Activities
Key Deliverables
Initiation
Creating a project charter and
business case
Stakeholder identification
Planning
Defining roles, defining
stakeholders and setting goals
Project work plan
Execution
Beginning of work
Delivering the stated project
Monitoring & controlling
Monitoring of project status
Reporting Project status
Closure
Checking if the project
objectives have been met
Delivering the project to the
project sponsor
Phase
Reviews
Entry Criteria
Exit Criteria
Initiation
Needed in order for
project to start
Broadly define the
project and secure buy-
in
Creating a project
charter
Planning
Needed to give the
direction the project
will take
Create the project
roadmap
Ensuring the project has
all the paper work
needed
Execution
This phase is needed for
the project to be
complete
Launch the project
using information from
the first two steps
Quality assurance team
checks on the project to
make sure it meets the
criteria that are set
Monitoring &
controlling
This phase is important
to ensure that the
project meets the
quality needed
Monitor whether the
project meets the
objectives
Check whether the
project meets the
project deliverables
stated
Closure
Closure marks the end
of the project
Meet the stakeholders
All stakeholders to sign
to proof they are
satisfied
Development Approaches:
Deliverable
Development Approach
Design of 19 km of route, including 10 km
underground
Iterative
Stations and stops built and equipped with
all necessary facilities
Agile
Public lighting at each station and stop
Agile
Communication and signaling system
implementation
Iterative
Bicycle parking spaces
Agile
Road infrastructure improvements
Agile
Subsidiary Management Plans:
Name
Comment
Scope
The project scope will be defined by the project
manager and project stakeholders
Time
Each milestone or activity will have enough time
to ensure quality
Cost
The cost will be managed within the stated budget
by using bottom-up estimation method
Quality
Quality assurance officers will ensure that the
project meets quality standards
Resource
The project resources will be managed by the
project manager
Communications
A communication plan will be drafted for the
project team members
Risk
Risk assessment plan will be developed to state all
the project risks
Procurement
The procurement officer will be responsible for
procuring materials
Stakeholder
The project stakeholders will be given different
roles
Other Plans
Project manager will state any other plans
Variance Thresholds:
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help
Scope Variance Threshold
Any change that will be made should be
recorded
Scope Baseline Management
There will be a written agreement of the
expectations and requirements of project
stakeholders.
Schedule Variance Threshold
The schedule variance that would be accepted
should not be more than 10 percent
Schedule Baseline Management
The project manager will retain a copy of the
original estimates, completion dates, start dates,
and other information the project manager may
wish to baseline
Cost Variance Threshold
The cost variance should not be more than 10
percent of the estimated budget
Cost Baseline Management
The project manager should use best cost
estimation techniques
Baselines:
schedule, cost, and scope
Attach all project baselines