Project Management Life Cycle-Iterative & Home / Project Management Life

Adaptive Cycle-Iterative & Adaptive

 10/12/2019  Seema Sonkiya

 Organizational In uences and Project Life Cycle, PMP®  21 Comments

All projects across industries follow a life cycle approach. Often I have
seen there are so many questions in mind for many
PMP® Certi cation aspirants on di erent types of life cycles. Why do
we need anything other than a predictive life cycle, which goes quite
sequential and looks perfect? What are these buzz words, i.e., iterative
& adaptive? What these new life cycles do di erently? Let’s clarify all
these doubts in this blog and be ready to answer all the questions
revolving around it.

First of all, we shall look at what is a Predictive Life Cycle according to

the PMBOK® Guide:

Predictive Life Cycle: A form of project life cycle

in which the project scope, time, and cost are
determined in the initial phases of the life cycle.

In summary, in this life cycle, we can predict the full ow of work.  We

can predict the nal product, and we know how we have to work to
deliver the right product.

In this way, we can follow a sequence of work like:

We start with requirement analysis and then move to the design of
the product. And after getting the approval of the design we move to
the development and nally, after testing, we deliver the product to
the customer.

Here in this life cycle, each phase focus on one type of work. And at
the end of the last phase,  we deliver the nal product to the
customer.

You can see we are sequencing phases of work. And, If we need any
feedback, it comes from the successor phase to the previous one. 
Like Requirement Analysis gets feedback from the design phase.

In this predictive life cycle, expected changes are minimal because

work is quite predictive and known. We can say the life cycle is quite
foretelling like technology is proven; the team is matured in
estimation techniques. Etc.

In other words, the team knows where they are heading? And what
they need to follow the sequence.  It is a plan-driven life cycle, where
we plan work upfront, and we make changes as an exception. It’s like
a yearlong project will have Planning, Analysis, Design, Code, testing
phases one by one and then the nal result is delivered over a year.

We don’t expect the long feedback cycle where testing is giving

feedback to requirement analysis. If it happens, this life cycle is not
right for us.  This long feedbacks introduces a lot of waste as we need
to lot of rework in requirement analysis, design, and development
also. When we are developing some new recipes, this long feedback is
common, and we should avoid the predictive life cycle. Here, we can
see in this new recipe, as things are not predictable, and we need a
di erent approach.  Now the question is, which life cycle is suitable
when requirements are abstract? The answer is the iterative life cycle.
We will discuss this life cycle later in this blog.

Now we are clear how this most common life cycle work. Let’s go to
the next step. What is an iterative life cycle?

Based on PMBOK® Guide:

“Iterative Life Cycle: A project life cycle where

the project scope is generally determined early
in the project life cycle, but time and cost
estimates are routinely modified as the project
team’s understanding of the product increases.
Iterations develop the product through a series
of repeated cycles, while increments
successively add to the functionality of that
product”

This life cycle believes in creating multiple learning opportunities. So,

here, the goal is to take frequent feedbacks before reaching the nal
product. This feedback helps the team to learn about the customer’s
and other stakeholder’s expectations. This life cycle understands that
requirements are abstract. And, real feedback comes when the
customer and other stakeholders can see some deliverable or part of
the product.

In summary, this life cycle says –

We cannot create a complete product using the approved
requirements only; we need to show and take feedbacks frequently. 
We need to learn continually and re ne the product base on these
learnings.
It is an example of repeatedly development and re nement and
makes this life cycle iterative. We move to the nal product after
continuous re nements or iterations. And, as a result of feedback, we
are open to the changes to any developed part of the product.
Changes are not an exception here. these are welcome in iterative
development.

We move to the next iteration after adapting the backlog based on

learnings that come from the feedbacks.

We deliver a result at the end of each iteration; we don’t wait to

provide a complete result or product at the end of the project. We
develop and re ne iteratively and demo it to get learning
opportunities. In this way, this process helps in delivering the right
product.

Like a yearlong project will have three months iterations. And, each
iteration will execute Planning, Analysis, Design, Code, testing phases,
and deliver the result at the end of the iteration.  This delivered result
may not be usable, but it is shown to give a feel for the nal product.
This feeling encourages a discussion of a product that will really solve
the problem.

This discussion generates feedback and Based on this feedbacks; the

backlog is adapted. This creates a re ned product using further
iterations.

Now, the question is – when do we need this iterative development?

We need it when requirements are abstract. And, we are not

con dent what exactly customer requirements are? We need this life
cycle where changes in the scope need to be managed. To manage
the scope, as we move based on continuous learning, changes in this
life cycle are naturally implemented in upcoming iterations rather
than an exception.

With this life cycle, project phases proceed through sequential or

overlapping mode in every iteration. And, the end result is delivered
at the end of each iteration.

So, if we are doing something new and we need to see where we are
moving and how this product is going to look and how will it solve –
We allow using that half-cook product before investing further.

Now come to the incremental life cycle:

“Incremental Life Cycle: An adaptive project life

cycle in which the deliverable is produced
through a series of iterations that successively
add functionality within a predetermined time
span. The deliverable contains the necessary &
sufficient capability to be considered complete
only after the final iteration.”

In simple words, it is like we need to develop ten things, we develop

them one by one instead of picking all in one go. This life cycle
delivers features incrementally, and whatever we develop, it is usable
and consumable.

Ok, we now understand these three bits, i.e. Predictive, Iterative and
incremental.   This is pretty much everything one can do, then what
this adaptive life cycle is?

Based on PMBOK® Guide:

Adaptive Life Cycle: The project life cycle that is

iterative and incremental.

It means this life cycle is a mix of iterative and incremental

development. We add features incrementally, but they can be
changed based on received feedback.

Using this life cycle, whatever is we deliver–

It is usable like incremental, but we are open for feedbacks and

re nements based on those feedbacks. These re nements can be
done either in iterations or we can follow a kanban or lean based
approach.

For more details, on how incremental and iterative development goes

together in Agile, or what does iterative mean in agile?
Do refer Incremental Or Iterative – Taking A Pragmatic Approach

If you have a question about an example of an adaptive strategy?

Then we can see, an adaptive life cycle is a change-driven. It is an Agile

way of doing things as it is intended to the high level of changes. It
needs on-going stakeholder’s involvement. Here iterations are very
rapid usually with a duration of 2 to 4 weeks and are fixed in time and
cost.

This life cycle is used for projects where rapid changes are expected
and scope is not possible to de ne upfront. So, change during the
project is naturally handled in rapid iterations.

Also, the end result is delivered at the end of each 2-4 week iteration.

Like, a yearlong project will have multiple 2-4 week iteration and each
iteration will execute Planning, Analysis, Design, Code, testing phases
and deliver the result at the end of the iteration.

Here is the comparative analysis between predictive, iterative, and

adaptive:
Let’s quickly recap the similarities and di erences of all these three
types of life cycles

Particular Predictive Iterative Adaptive

Stages/ Can happen Can Can happen

Phases sequentially or happen sequentially or
overlap sequentially overlap
or overlap

Stages/Phases Planning/ Planning/ Planning/

Analysis/ Analysis/ Analysis/ Design/
Design / Code/ Design/ Code/ testing all
testing all takes Code/ takes place
place testing all
takes place

Scope Defined upfront Defined for The scope is set

at the beginning upcoming in the form of
iteration features from
and high- which features
level vision are picked for the
for the rest current iteration

Change At initial Taken care Taken care even

phases/stages with less more rapid
can be cost impact changes every 2-
accommodated. during the 4 weeks with less
Cost overruns planning of cost impact
as late it comes the next during the
up during iteration planning of the
project next iteration
Lifecycle

Risk The risk of The risk of The risk of

change/ change/ change/
feedback is feedback is feedback is least
huge at later less as as iterations are
stages/ phases iterations too small and
reduce it reduce it
naturally naturally

Customer Customer Customer Customer

 Feedback feedback is feedback is feedback is
received at the received at received at the
end of the the end of end of each rapid
project only and each iteration.
customer iteration Customers are
involvement is with which involved/engaged
more at the customers continuously
beginning and are
end involved
multiple
times
during the
project

Complexity Used for Used Used in a rapidly

projects where where a changing
the product to change in environment,
be delivered is objectives/ where scope/
well understood scope need requirements are
and to be difficult to define
complexities managed in advance and
are not there to and possible to define
handle complexity small increments
reduction is
required as
the project
progresses

Delivery/Value Delivery Delivery Delivery happens

happens at the happens at very rapidly after
end only once the end of every 2-4 weeks
and the each and customer get
customer gets iteration the value
value at the end and delivered very
customer frequently
gets value
early in the
project

This is how the world is moving, especially in the software industry.

The transition is happening from predictive to iterative to adapt ve I
.e.an agile way of working. PMBOK® Guide also included avors of
Agile in it in the form of the adaptive life cycle. The ever-changing
needs of customers and the inability to foresee the market and
predict the behavior are the key driver to make this transition.

You can watch and listen to the live video presentation on predictive,
iterative and adaptive life cycles here:

You can join the discussion on the same in our Forum. You can also
log in to our YouTube channel watch the video on the same

Enroll to our FREE PMP® Certification Introductory

Program to learn more about PMP® certification

ADAPTIVE LIFE CYCLE LIFE CYCLE PMP®

PREDICTIVE LIFE CYCLE PROJECT LIFE CYCLE

21 comments

Seema Sonkiya
20/02/2020 AT 4:17 AM

Hi Dhilkesh,
Greetings!!
Thanks for your kind words, keep exploring iZenBridge resources.

Regards,
Seema

Dhikesh
18/02/2020 AT 5:19 PM

Thanks for the explanation. It is Cristal clear

Seema Sonkiya
23/12/2019 AT 11:35 AM

Thanks Michael, happy to know that blog was valuable to you!!

Michael
21/12/2019 AT 5:09 PM

Fantastic explanation of the di erent lifecycles my friend. I love

the way you discussed it in terms of meal preparation and
delivery. That makes is so easy to grasp. Thank you!

Seema Sonkiya
10/12/2019 AT 6:20 AM

Thanks Prateek for your kind words!!

Prateek Mathur
08/12/2019 AT 7:42 AM

so well explained with examples that makes it even easier to

understand. Wonderful video… Thanks for sharing.

Seema Sonkiya
25/09/2019 AT 8:15 AM

Thanks Roae for your kind words 🙂

Seema Sonkiya
25/09/2019 AT 4:45 AM

Hi Tinashe,
Greetings!!

These are di erent approaches. When you can predict your

requirements and when you can predict how to achieve those
requirements, you can use predictive life cycle. In case, you cannot
predict your future with 100% con dence, in that case you need to
go with adaptive life cycles.

Regards,
Seema

Rose Hahn
25/09/2019 AT 4:10 AM

Thanks for sharing an informative post.

Tinashe Chikomo
23/09/2019 AT 12:45 AM

Thank you for the article. What is the general relationship

between predictive and adaptive life cycles?

Seema Sonkiya
18/09/2019 AT 1:43 PM

Hi Ashvini,
Greetings!!

Thanks for contacting us!!

Yes, In Overlapping next phase starts before the completion of the
previous one.
Regards,
Seema

Ashvini
13/09/2019 AT 5:01 AM

Iterative , adaptive & incremental as a life cycle is explained here. I

would like to understand the di erence between iterative &
overlapping phase & the de nition of iterative phase. I came
across these terms in PMBOK’s page 19 as well as in 1 practice
question. In overlapping, more than 1 are active but their start
dates & nish dates are di erent. Is my understanding correct
about overlapping phase

Seema Sonkiya
12/02/2019 AT 10:30 AM

Thanks Hitesh, good to you you found value in it.

hitesh sethi
11/02/2019 AT 11:01 AM

Great explanation of the concept which none of the books seem

to provide in this way. Thanks a lot.

Sunil Pandey
29/09/2017 AT 3:38 AM

Excellent explanation Sir. Cleared all doubts.

Thanks u so much.

Seng Chye
13/09/2017 AT 1:44 PM

Simple & Clear cut. Yet all encompassing explaination. Thank you
very much.
Ashutosh Ghildiyal
21/12/2016 AT 7:28 AM

Thanks, the video did help in making the understanding better.

Also was looking for real example than general explanation.
Example like Construction of a house may come under predictive
life cycle, Construction of a Sports stadium (in case this example is
correct) under iterative and for adaptive life cycle..?

Seema Sonkiya PMI PBA

21/12/2016 AT 5:51 AM

Please watch following video, it will give many examples of

adaptive life cycle: https://www.youtube.com/watch?
v=mAqHTn7LnOg

Ashutosh Ghildiyal
21/12/2016 AT 5:33 AM

Can someone give a simple example/ilustration

of an adaptive life cycle

Saket Bansal
23/11/2015 AT 10:37 AM

Thank you for your comment , checkout our discussion forum for
PMP related topics , forum.izenbridge.com

Nitika
19/11/2015 AT 10:18 PM

Nice explanation. covered with a nice explanation and perfect

pictorial diagram. thanks again
Leave a Reply

Comment

Name *

Email *

Website

POST COMMENT