Project Life Cycle

DR. RISHABH RATHORE, ASSISTANT PROFESSOR

ICFAI BUSINESS SCHOOL
Paper Details
Archibald, R. D., Filippo, I. di, & Filippo, D. di. (2012). The Six-Phase Comprehensive Project
Life Cycle Model Including the Project Incubation/Feasibility Phase and the Post-Project
Evaluation Phase. PM World Journal Six-Phase Comprehensive Project Life Cycle Model, I.
www.pmworldlibrary.net

Available on: https://pmworldlibrary.net/wp-content/uploads/2013/08/PMWJ5-Dec2012-

ARCHIBALD-DI-FILIPPO-Featured-Paper.pdf
Introduction
A company that wants to compete in the international market knows the importance of adopting
a Business Process Management (BPM) model as a holistic management approach.
The BPM Model is the set of activities needed to define, optimize, monitor and integrate
business processes in order to create the desired outcome for each stakeholder.
In addition to driving a company’s on-going operations, Business Process Management drives
its projects and programs, integrated with their multi-project portfolios to achieve high
performance development that is characterized by new success criteria, where project
management metrics are based on performance indices as shown by a matrix between KPIs and
CSFs
Key Performance Indicators (KPIs) are commonly used by an organization to evaluate its success or the
success of a particular activity in which it is engaged.
Critical success factor (CSF) is the term for an element that is necessary for an organization or project
to achieve its mission successfully, and for ensuring the success of a company.
Introduction
In achieving improved success in project, program, and portfolio management there
are two desirable goals:

◦ A new way to define more broadly and manage more comprehensively the Project
Life Cycles for both the transformational and the delivery projects and programs
within an enterprise; and

◦ The proper and effective use of Information Technology (IT) with Business Process
Management (BPM) plus Project, Program and Portfolio Management (PPPM.)
Project versus Product Life Cycle
Management
Purposes of Project Life Cycle Process
Models:
◦ Enable all persons concerned with creating, planning and executing projects to understand
the processes to be followed throughout the life of the project.

◦ Capture and document the best experiences within the organization so that the processes
within each project phase can be improved continually and applied on future similar projects.

◦ Enable all the project roles and responsibilities and the project planning, estimating,
scheduling, monitoring and control methods and tools to be appropriately related to the
overall project life cycle management process; this includes most importantly assigning
qualified persons to the roles of Project Executive Sponsor and Project Manager at the proper
points in the project life cycle phases, as discussed later in this paper.

◦ Enable the effective application of project management software application packages that
are integrated with all appropriate corporate information systems.
Life Cycle Phases and Decision Points
◦ Starting the project (concept, authorization, initiation, identification,
selection, project charter and business case, planning, scheduling.)

◦ Organizing and Preparing (definition, feasibility confirmation,

development, demonstration, design prototype, quantification.)

◦ Carrying out the work (execution, implementation, realization, production

and deployment, design/construct/ commission, installation and test.)

◦ Closing the project (handover of the project results to the user, project
termination, sometimes including post-completion evaluation.)
Extended life cycle

Figure. A second
“standard” project
and extended life
cycle model. (APM
2006 p 80.)
Types of Life Cycle Model
1. Predictive Life cycle model
2. Adaptive Life cycle model
3. Iterative Life cycle model
4. Increment Life cycle model
Types of Life Cycle Model
1. Predictive Life cycle model
2. Adaptive Life cycle model
3. Iterative Life cycle model
4. Increment Life cycle model
Predictive Life Cycle Model
Predictive Life Cycle Model
Predictive life cycle models “favor optimization over adaptability” (Desaulniers and Anderson
2002) and include:
◦ Waterfall (also known as traditional and top-down): linear ordering of the phases, which
can be strictly sequential or overlapping to some extent; no phase is normally repeated.

◦ Prototyping: functional requirements and physical design specifications are generated

simultaneously.

◦ Rapid Application Development (RAD): based on prototyping and iterative development

with no specific planning involved. The process of writing the software itself involves the
planning required for developing the product.

◦ Incremental Build: a method of software development where the product is designed,

implemented and tested incrementally (a little more is added each time) until the product is
finished.
Types of Life Cycle Model
1. Predictive Life cycle model
2. Adaptive Life cycle model
3. Iterative Life cycle model
4. Increment Life cycle model
Adaptive life cycle models
Adaptive life cycle models
SCRUM PLC
◦ Scrum is an Agile project management methodology involving a small team led by a Scrum
master, whose main job is to remove all obstacles to getting work done.

◦ Work is done in short cycles called sprints, and the team meets daily to discuss current tasks
and any roadblocks that need clearing.

◦ Traditional project management methods fix requirements in an effort to control time and
cost; Scrum on the other hand, fixes time and cost in an effort to control requirements.

◦ This is done using time boxes, collaborative ceremonies, a prioritized product backlog, and
frequent feedback cycles.

◦ The involvement of the business throughout the project is critical as Scrum relies heavily on
the collaboration between the team and the customer or customer representative to create
the right product in a lean fashion.
SCRUM PLC

• Refer the following link to get more idea:

• https://www.orangescrum.com/blog/agile-project-management-with-scrum-boards-
backlog-sprints-in-orangescrum.html
Figure. NASA’s Project Life Cycle Process. See
http://spacese.spacegrant.org/uploads/Project%20Life%20Cycle/PPF_WallChart_color.pdf
for a very detailed wall chart that expands this simplified version.
Figure. Spiral software development
project life cycle model. Source:
http://commons.wikimedia.org/wiki/Categ
ory: Spiral_model_of_Boehm?uselang=en
Adaptive life cycle models
Adaptive life cycle models “accept and embrace change during the development process and
resist detailed planning” (Desaulniers and Anderson 2002) and include:

◦ Adaptive Software Development/ASD: Mission driven, component based, iterative cycles, time
boxed cycles, risk-driven, and change-tolerant. The IBM Rational Unified Process (RUP), driven by
risk and customer need is a good example of an adaptive software development model.

◦ Spiral: Repetition of the same set of life-cycle phases such as plan, develop, build, and evaluate
until development is complete.

◦ Extreme Programming/XP: Teams of developers, managers, and users; programming done in

pairs; iterative process, collective code ownership.

◦ Agile and SCRUM: Similar to above adaptive life cycle models with iterations called “sprints” that
typically last one week to 30 days with defined functionality to be achieved in each sprint; active
management role throughout.
Types of Life Cycle Model
1. Predictive Life cycle model
2. Adaptive Life cycle model
3. Iterative Life cycle model
4. Increment Life cycle model
Iterative Life cycle model
Iterative Life cycle model
Types of Life Cycle Model
1. Predictive Life cycle model
2. Adaptive Life cycle model
3. Iterative Life cycle model
4. Increment Life cycle model
Increment Life cycle model
Increment Life cycle model

An iteration in itself could be complete but might not

much use when its standalone
Types of Life Cycle Model
1. Predictive Life cycle model
2. Adaptive Life cycle model
3. Iterative Life cycle model
4. Increment Life cycle model
https://www.youtube.com/watch?v=I4fAFcPCw6k
Types of Project Management Life Cycle - Adaptive, Predictive, Iterative, Incremental and
Hybrid

https://www.youtube.com/watch?v=bwfW7_56dqU
Video title Why Agile Approach? Difference between Iterative, Incremental and Agile
Book Details
The Project Management Life Cycle By Jason Westland (A book review by R. Max Wideman)

Available on: http://www.maxwideman.com/papers/life_cycle/life_cycle.pdf

The four phases of the project life cycle
Project initiation activities
Project initiation activities
Project initiation activities
Project initiation activities
Project initiation activities
Project Planning Activities
Project
Execution
Project Closure
Project Statement of Work and Project
Charter
Project Statement of Work (SOW)
◦ Statement of Work (or SOW) is a formal document that defines the
entire scope of the work involved for a vendor and clarifies deliverables, costs,
and timeline.

◦ It is needed in situations where a project involves vendors and external

contributors in addition to the internal project team.

◦ You usually create a SOW as part of a bid document or part of a contract. It is

vital that the SOW is clear to all stakeholders in order to clarify the metrics for
success and to avoid disputes involving deliverables, budgets, or timelines.
Project Statement of Work (SOW)
The statement of work should include:
◦ All deliverables and due dates.
◦ The individual tasks that lead to the deliverable, and who these tasks are
assigned to.
◦ The resources needed for the project including facilities, equipment, and QA
procedures.
◦ The governance process for the project.
◦ Costs and deadlines for payment.
Project SOW
Project Charter
The Project Charter is a formal document to authorize the project and give the
project manager the authority to spend the project budget.

The Project Charter includes:

• Project purpose / justification

• High-level project objectives and product characteristics
• Project success criteria
• High-level requirements
• High-level schedule and budget
• Name the Project manager
• List out the project approval requirements and approval authority
Project Charter
•The Project Charter is created in the Develop Project Charter process with the
following inputs:

• Project statement of work (SOW)

• Business case
• Agreement
• Enterprise environmental factors (EEFs)
• Organizational process assets
Illustrated Example
Imagine you are the senior management of your exam prep project and you are
to create the Project Statement of Work and the Project Charter for your project
manager

The Project Statement of Work would likely to include:

◦ Be qualified for the exam (e.g. 35 Contact Hours of project management education; working
experience; etc.);
◦ Be well prepared for the exam through studying and mock exam taking;
◦ Sit and pass the exam in first try to get the credential.
Illustrated Example
Imagine you are the senior management of your exam prep project and you are
to create the Project Statement of Work and the Project Charter for your project
manager

The Project Charter would contain similar items:

◦ Project purpose: Be able to pass the exam and get PMP® certified as this would add
competitive advantages to the project management career
◦ Project success criteria: pass the exam in first try
◦ High-level schedule and budget: study and take the exam within 3 months (which is
the norms for practising project managers), the minimal certification cost for the
exam prep and exam is around US$1000
◦ Project manager: you
Work Breakdown Structure
◦ Breaking work into smaller tasks is a common productivity technique used to
make the work more manageable and approachable.

◦ For projects, the Work Breakdown Structure (WBS) is the tool that utilizes
this technique and is one of the most important project management
documents.

◦ It singlehandedly integrates scope, cost and schedule baselines ensuring that

project plans are in alignment.
Work Breakdown Structure
◦ The Project Management Institute (PMI) Project Management Book of
Knowledge (PMBOK) defines the Work Breakdown Structure as a “deliverable
oriented hierarchical decomposition of the work to be executed by the project
team.”

◦ There are two types of WBS: 1) Deliverable-Based and 2) Phase-Based.

◦ The most common and preferred approach is the Deliverable-Based approach.

The main difference between the two approaches are the Elements identified
in the first Level of the WBS.
Work Breakdown Structure
• Deliverable-Based Work Breakdown Structure
• A Deliverable-Based Work Breakdown Structure clearly demonstrates the relationship
between the project deliverables (i.e., products, services or results) and the scope (i.e., work
to be executed).
• In the deliverable-based WBS, the project phases are divided into project deliverables and
work packages
Work Breakdown Structure
Deliverable-Based Work Breakdown Structure

In figure, the Level 1 Elements are summary deliverable descriptions. The Level 2 Elements in each Leg of
the WBS are all the unique deliverables required to create the respective Level 1 deliverable.
Work Breakdown Structure

Phase-Based Work Breakdown Structure

• The phase-based WBS displays the final deliverable on top, with the WBS levels
below showing the five phases of a project (initiation, planning, execution, control
and closeout).

• Just as in the deliverable-based WBS, the project phases are divided into project
deliverables and work packages.
 Work Breakdown Structure
Phase-Based Work Breakdown Structure
 Work Breakdown Structure
Phase-Based Work Breakdown Structure

• A good WBS is simply one that makes the

project more manageable.
• Every project is different; every project
manager is different and every WBS is
different. So, the right WBS is the one that
best answers the question, “What
structure makes the project more
manageable?”
How to Make a Work Breakdown
Structure?
A good Work Breakdown Structure is created using an iterative process by
following these steps and meeting these guidelines:
How to Make a Work Breakdown Structure?
How to Make a Work Breakdown Structure?

Reference: https://www.workbreakdownstructure.com/
MindView Mind Mapping Software
YouTube Reference Link:
Creating a Work Breakdown Structure WBS in MindView Mind Mapping
Software
https://www.youtube.com/watch?v=cULMKqVh3QE&t=199s