APM PMQ - Section 1.1 - Life Cycles
Exam Questions and Answers with
Verified Solutions | Latest Updated 2026
A framework of distinct Life cycle (APM definition)
high-level stages used to turn
an idea or concept into reality
in an orderly and efficient
manner; it underpins how
project work is structured and
organised.
Projects vary in certainty, risk Life cycles-why different approaches
and clarity of scope: linear exist
suits predictable/known
requirements; iterative suits
uncertainty and evolving
scope; hybrid blends both
where different parts need
different approaches.
Concept (business case) → Linear project life cycle-phases (and
Definition (project what they produce)
management plan, PMP) →
Deployment (build outputs;
may have stage reviews) →
Transition (commissioning,
handover into BAU, closure
and acceptance).
, When outputs are clearly Linear life cycle-when is it
defined and the environment applicable?
is stable/low risk, needing
early definition of
requirements and strong
control/governance.
Adaptive delivery that Iterative life cycle-what it is and
assumes change and evolving when applicable
understanding of scope; best
when objectives evolve or
scope is vague/uncertain
(common in software/digital),
using repeated iterations with
frequent user feedback.
Pre-project/Feasibility/Foundati Iterative life cycle-typical high-level
ons → Evolutionary stages
development (iterations) →
Deployment → Post-project.
A short, fixed period where the Timebox / sprint (iterative)
team completes work and
reviews outcomes; feedback is
used to adjust the next
iteration.
A blend of linear structure with Hybrid life cycle-what it is and when
iterative elements; useful applicable
when overall governance
needs linear phases but parts
of the work (e.g.,
design/development) benefit
from iteration and feedback.
Exam Questions and Answers with
Verified Solutions | Latest Updated 2026
A framework of distinct Life cycle (APM definition)
high-level stages used to turn
an idea or concept into reality
in an orderly and efficient
manner; it underpins how
project work is structured and
organised.
Projects vary in certainty, risk Life cycles-why different approaches
and clarity of scope: linear exist
suits predictable/known
requirements; iterative suits
uncertainty and evolving
scope; hybrid blends both
where different parts need
different approaches.
Concept (business case) → Linear project life cycle-phases (and
Definition (project what they produce)
management plan, PMP) →
Deployment (build outputs;
may have stage reviews) →
Transition (commissioning,
handover into BAU, closure
and acceptance).
, When outputs are clearly Linear life cycle-when is it
defined and the environment applicable?
is stable/low risk, needing
early definition of
requirements and strong
control/governance.
Adaptive delivery that Iterative life cycle-what it is and
assumes change and evolving when applicable
understanding of scope; best
when objectives evolve or
scope is vague/uncertain
(common in software/digital),
using repeated iterations with
frequent user feedback.
Pre-project/Feasibility/Foundati Iterative life cycle-typical high-level
ons → Evolutionary stages
development (iterations) →
Deployment → Post-project.
A short, fixed period where the Timebox / sprint (iterative)
team completes work and
reviews outcomes; feedback is
used to adjust the next
iteration.
A blend of linear structure with Hybrid life cycle-what it is and when
iterative elements; useful applicable
when overall governance
needs linear phases but parts
of the work (e.g.,
design/development) benefit
from iteration and feedback.
