Project Life Cycle

Download as ppt, pdf, or txt
Download as ppt, pdf, or txt
You are on page 1of 10

Project Life Cycle

Introduction
The Project Life Cycle refers to a logical
sequence of activities to accomplish the
project’s goals or objectives.

Regardless of scope or complexity, any


project goes through a series of stages
during its life.
Project Life Cycle

I II III IV
I. Initiation
• Scope of the project is defined along with the
approach to be taken to deliver the desired outputs.

• Project manager is appointed and in turn, he


selects the team members based on their skills and
experience.

• Common tools or methodologies used in the


initiation stage are Project Charter, Business Plan,
Project Framework (or Overview), Business Case
Justification.
Phase-I Summary
• Identification of the need
• Establishment of the primary feasibility of
project idea
• Identification of alternatives
• Evaluation (appraisal) of the alternatives
• Investment decision
II. Planning
• It should include a detailed identification and
assignment of each task until the end of the
project.
• It should also include a risk analysis and a
definition of a criteria for the successful
completion of each deliverable.
• Governance process is defined, stake holders
identified and reporting frequency and channels
agreed.
• Tools used in the planning stage are Business Plan
and Milestones Reviews.
Phase-II Summary
• Blue print for the execution of the project is
ready.

• The output of phase II is usually called the


Detailed Project Report (DPR).

• Intensity of activities continuously rises.


III. Execution and controlling
• During the execution phase, the planned solution is implemented to solve
the problem specified in the project's requirements.

• In product and system development, a design resulting in a specific set of


product requirements is created.

• This convergence is measured by prototypes, testing, and reviews.

• As the execution phase progresses, groups across the organization become


more deeply involved in planning for the final testing, production, and
support.

• The most common tools or methodologies used in the execution phase are
an update of Risk Analysis and Score Cards, in addition to Business Plan
and Milestones Reviews.
IV. Closure
• In this last stage, the project manager must ensure that the
project is brought to its proper completion.
• The closure phase is characterized by a written formal project
review report containing the following components:
– a formal acceptance of the final product by the client
– Weighted Critical Measurements (matching the initial
requirements specified by the client with the final delivered
product)
– rewarding the team
– a list of lessons learned, releasing project resources
– a formal project closure notification to higher management.

No special tool or methodology is needed during the closure


phase.

You might also like