PROJECTS MANAGEMENT

PLAN
PROJECT SCOPE

Business Purpose, Objectives and Goals: A

concise statement of the project purpose, objectives
and goals. This information should come from the
Project Leader.

Problem/Opportunity Statement:
Problem/Opportunity Table from the Project Leader.
PROJECT CONSTRAINTS
Inclusions: Indicate key deliverables,
requirements and/or functionality that the
project is committed to delivering. Information
should come from Project Leader .
Exclusions: Indicate key deliverables,
requirements and/or functionality that is
explicitly excluded from the projects scope.
Information should come from Project Leader.
Key Assumptions: Specify any assumptions
that are driving the project approach.
Information should come from Project Leader.
RISK/ISSUE/DEPENDENCY
Risk/Issue Impact Mitigation Strategy

Risk: Describe risk Explain the probability and Outline steps being taken or

potential impact on project, planned to reduce the

including effect on benefits, probability/impact of the risk.

scope, time or cost.

Issue: Describe issue Explain impact on project, Outline steps being taken or

including effect on benefits, planned to resolve the issue.

scope, time or cost.

Outline the communication
Dependency: Describe Explain how the project and

dependency depends on an external other plans for keeping the

effort, or how an external efforts coordinated.

effort depends on the

project.
 PROJECT PROGRESS REPORT

Date Project Name Project Leader

Key Phases Progress Status Finish
Project Summary
Project Initiation
90% On Track 12-Mar-15
Project Planning Possible
70% Delays 15-Apr-15
Project Execution
43% Delayed 18-Aug-15
Project Monitoring and
Control 26% Complete 20-Sep-15
Project Closure
78% On Track 03-Nov-15

Task Completed Tasks Delayed Tasks Planned

Key Project Risks & Issues

Type
Risks or Issue Description
The vendor has indicated that there could be delays in the product being ready in time. Delays from the vendor side
Risk means project schedule could be delayed.
Issue Some unplanned leaves have been taken by the project team. There could be some impact to the schedule.
PROJECT ORGANIZATION
Mr. Rajeev Saxena (FH-Logistics
STEERING
COMMITTEE Mr. Pradeep Singh(DH-Logistics)

Mr. Saurav Bose

CONVENOR

Each Individual Project has a project

LEADER Leader

Each Individual Project Consists of 4-5

TEAM
MEMBERS
team members.
KEY ROLES AND RESPONSIBILITIES

Steering
CONVENOR LEADER
TEAM
Committee MEMBERS
Provides strategic Call regular Develop a strategy understanding the
advice regarding committee meetings, the team will use to purpose and
trade off decisions either on a monthly reach its goal objectives of the
and issue resolution schedule or as Listen to team project
Actively participates needed. members' feedback reporting progress
in regular Prepare an agenda Monitor team against plan
assessment of overall for each meeting and members' producing the
project health E-mail it to members participation to deliverables/products
discussions and before your next ensure the training to agreed
meetings to ensure: meeting. they are being specifications
Project vision is on Keep a record of the provided is being put reviewing key project
track agendas and minutes into use, and also to deliverables/products
Impact of each meeting. see if any additional identifying issues &
Assessments Prepare a time line training is needed risks associated with
so that everyone will Manage the flow of the project
know what is due day-to-day working together as
when. operations a team
Create report to Healthy & successful
update on teams communication
progress
 Project Initiation Phase a project is formally started, named and defined at a broad level
during this phase. Project sponsors and other important stakeholders due diligently decide
whether or not to commit to a project. Depending on the nature of the project, feasibility studies
are conducted. Or, as it may require, in an IT project requirement gathering and analysis are
performed in this phase. In the construction industry a project charter is completed in this phase.

Project Planning Phase a project management plan is developed comprehensively of

individual plans for cost, scope, duration, quality, communication, risk and resources. Some of
the important activities that mark this phase are -making WBS, development of schedule,
milestone charts, GANTT charts, estimating and reserving resources, planning dates and modes
of communication with stakeholders based on milestones, deadlines and important deliveries. A
plan for managing identified and unidentified risks is determined as this may affect aspects of a
project later on. Risk management planning includes: risk identification and analysis, risk
mitigation approaches, and risk response planning.

Project Execution Phase a project deliverable is developed and completed, adhering to

a mapped-out plan. A lot of tasks during this phase capture project metrics through tasks like
status meetings and project status updates, other status reports, human resource needs and
performance reports. An important phase as it will help you understand whether your project will
be a success or failure.

Project Monitoring and Control Phase occurring at the same time as the execution phase,
this one mostly deals with measuring the project performance and progression in accordance to
the project plan. Scope verification and control occur to check and monitor for scope creep, change
control to track and manage changes to project requirement. Calculating key performance
indicators for cost and time are done to measure the degree of variation, if any, and in which case
corrective measures are determined and suggested to keep a project on track. To prevent project
failure, consider why projects are likely to fail and the ways to prevent failure.

Project Closure Phase A project is formally closed. It includes a series of important tasks such
as delivering the product, relieving resources, reward and recognition to the team members and
formal termination of contractors in case they were employed on the project.