HOW THE 12

PRINCIPLES
FEEDS INTO
THE
8
PERFORMANCE
DOMAIN
 8
Performance
Domain
 This performance domain entails establishing
2.3 DEVELOPMENT • Selecting a development approach consistent with the Project deliverable
APPROACH AND • Selecting a delivery cadence consistent with the Development approach and
LIFE CYCLE SELECTION the deliverable
PERFORMANCE DOMAIN • Selecting a project life consisting of phases that facilitates the delivery
cadence and development approach required to produce the deliverables
Deliverable. DEFINITION
Any unique and verifiable product, result, or capability to perform a
service that is required to be produced to complete a process, phase, or
project.

Development Approach.
A method used to create and evolve the product, service, or result during
the project life cycle, such as a predictive, iterative, incremental, adaptive,
or hybrid method.

Cadence.
A rhythm of activities conducted throughout the project.
Refers to the timing and frequency of project deliverables.

Project Phase.
A collection of logically related project activities that culminates in the
completion of one or more deliverables.

Project Life Cycle.

The series of phases that a project passes through from its start to its
completion.
 RELATIONSHIP BTW
DEVELOPMENT
The type of project deliverable will APPROACH,
determine the development CADENCE, AND
approach. LIFE CYCLE

The type of deliverable and the

development approach will
influence the delivery cadence

The development approach and the

delivery cadence will determine the
project life cycle and its phases.
Single Delivery. DELIVERY CADENCE
Projects that have a single delivery deliver at the end of the project

Refers to the timing and

frequency of project
deliverables.
Multiple Delivery.
A project may have multiple components that are delivered at different times.
A project to develop a new drug may have multiple deliveries, such as preclinical
submissions, Phase 1 trial, Phase 2, Phase 3, registration, and then launch.

Periodic Deliveries.
They have fixed delivery schedule, such as monthly or bimonthly. A new software
application may have internal deliveries every two weeks, and then periodic
releases into the market

Continuous Delivery
This is the practice of delivering feature increments immediately to customers,
often through the use of small batches of work and automation technology.
Continuous delivery can be used for digital products.
The emphasis is on delivering benefits and value throughout the product life
cycle. This works is best with project teams that are stable and remain intact.
 • A development approach is the means used to create and evolve the product, service, or result
DEVELOPMENT during the project life cycle.
• These approaches are often viewed as a spectrum where predictive anchors one end and agile
APPROACHES on the other.
• The range between these poles represents the hybrid approach, a blend of elements from both.
 THERE
ARE
Predictive THREE
COMMONL
Approach. Y USED
APPROAC
HES
Hybrid
approach.
Adaptive
approach.
Useful when the project and product requirements PREDICTIVE
can be defined, collected, and analyzed at the start
APPROACH.
Used when there is a significant investment
involved and a high level of risk that may require
frequent reviews, change control mechanisms

The scope, schedule, cost, resource needs, and risks

can be well defined in the early phases, and they
are relatively stable.

This development approach allows the project

team to reduce the level of uncertainty early in the
project and do much of the planning up front

Projects that use this approach have templates from

previous, similar projects.
Are useful when requirements are subject to a high level of uncertainty ADAPTIVE
and volatility
APPROACH
and are likely to change throughout the project

A clear vision is established at the start of the project,

and the initial known requirements are refined, detailed, changed, or

replaced in accordance

with user feedback, the environment, or unexpected events

Adaptive approaches use iterative and incremental approaches

the product is more likely to evolve based on stakeholder feedback.

agile approaches entail iterations that are 1 to 2 weeks in duration with a

demonstration of the accomplishments at the end of each iteration

The project team will determine the scope they can achieve based on a
prioritized backlog, estimate the work involved, and work collaboratively
throughout the iteration to develop the scope
Is a combination of adaptive and predictive approaches HYBRID
APPROACH
some elements from a predictive approach are used and some from an adaptive
approach are used

An example of a hybrid approach could be using an adaptive approach to develop a

product that has significant uncertainty associated with the requirements. However,
the deployment of the product can be done using a predictive approach.

Another example is a project with two main deliverables where one deliverable is
developed using an adaptive approach and the other using a predictive approach

An iterative approach is useful for clarifying requirements and investigating various

options.

An iterative approach may produce sufficient capability to be considered acceptable

prior to the final iteration

An incremental approach is used to produce a deliverable throughout a series of

iterations. Each iteration adds functionality within a predetermined time frame (a
timebox).

The deliverable contains the capability to be considered as completed only after the
final iteration.
CONSIDERATIONS FOR SELECTING A
DEVELOPMENT APPROACH

The product,
The project; The organization
service, or result;
 SELECTING A DEVELOPMENT APPROACH

The Product, Service,

The Project THE ORGANIZATION
or Result

Degree of innovation Stakeholders

Requirements certainty
Organizational
Scope stability Project team structure.
size and
Ease of change. Schedule location. .
constraints
Delivery options Organizational
capability. Culture.
Risk
Safety requirements Funding
availability.
Regulations
 QUESTION

You are working on a project where the requirements are clear but the solution ideas are
uncertain. The product owner and the technical experts can't be sure which ideas will work
in practice, and which ones won't. The organisation cannot afford to get this project wrong,
as they have previously made mistakes and customers are starting to leave. What will you do
next?
A. Use an Incremental development approach for the project.

B. Use an Iterative development approach for the project.

C. Use a Predictive development approach for the project.
D. Use a hybrid development approach for the project.
Project Life Cycle. L I F E CYCLE
The series of phases that a project passes through from its
start to its completion. AND PHASE
DEFINITIONS
Project Phase.
A collection of logically related project activities that
culminates in the completion of one or more deliverables.

the delivery cadence and the development approach will

determine the type and number of phases in a project life
cycle.

Phase Gate/Review/Exit Criteria.

Project phases often have a phase gate review (also known as
stage gate) to check that the desired outcomes or exit criteria
for the phase have been achieved before proceeding.

Exit criteria may tie to acceptance criteria for deliverables,

contractual obligations, meeting specific performance
targets, or other tangible measures
TYPICAL
PROJECT PHASES
IN A LIFE CYCLE
Interrelationship of need assessment and critical business & project document
• A life cycle where one phase
finishes before the next one
begins
• Each phase is only performed
once, and each phase focuses
on a particular type of work.
CHARACTERISTICS OF PREDICTIVE LIFE CYCLES

• Project activities often execute in a

serial manner, as shown
• The team creates detailed
requirements and plans at the
beginning of the project.
• They monitor and control changes
that might affect the scope,
schedule, or budget.
• Predictive projects do not typically
deliver business value until the end
of the project.
• Each subsequent build would add functionality to the initial build
 CHARACTERISTICS OF INCREMENTAL LIFE CYCLES

This reduces potential

rework and/or customer
dissatisfaction.

Optimize for speed of

delivery.

Frequent delivery of smaller

deliverables is called an
incremental life cycle

Providing a customer, a single feature or

a finished piece of work is an example of
the incremental approach
• At the end of each iteration (sometimes known as a sprint), the customer reviews a functional deliverable.
• At the review, the key stakeholders provide feedback, and the project team updates the project backlog of features and
functions to prioritize for the next iteration
CHARACTERISTICS OF ITERATIVE LIFE CYCLES

• Iterative life cycles uses prototypes or proofs of

concept to improve the product or result
• It allows for stakeholder feedback and team
insights.
• Iterative life cycles is used when complexity is high
with frequent changes,
• or when the scope is subject to differing
stakeholders’ views of the desired final product.
• Iterative life cycles may take longer because they
are optimized for learning rather than speed of
delivery
• Have you ever been involved on a project where
the requirements seemed to change daily and
thought, “We will know the requirements when
we deliver a prototype that the business
approves.”
Flow-Based Scheduling

• Flow-based scheduling, does not prescribe the use of life

cycle or phases
• One goal is to optimize the flow of deliveries based on
resource capacity, materials, and other inputs.
• Another goal is to minimize time and resource waste and
optimize the efficiency of processes and the throughput of
deliverables
• Projects that use these practices and methods usually adopt
them from the Kanban scheduling system used in lean and
just-intime scheduling approach
ALIGNING OF DELIVERY CADENCE,
DEVELOPMENT APPROACH, AND LIFE
CYCLE
 C H E C K I N G R E S U LT S

• How do you determine the development approaches

• How do you determine the project life cycle
consisting of phases that connect the delivery of
business and stakeholder value from the beginning
to the end
• How do you determine the Project life cycle phases
that facilitate the delivery cadence and development
approach
Checking Outcomes
Back-Up Slides
 • Projects often combine elements of different life cycles in
3.1.6 CHARACTERISTICS order to achieve certain goals.
• A combination of predictive, iterative, incremental,
OF HYBRID LIFE CYCLES and/or agile approaches is a hybrid approach.
• An example of this approach is the development of a new
high-tech product followed by rollout and training to
thousands of users.
 • A small agile element within a chiefly predictive
3.1.8 PREDOMINANTLY project.
PREDICTIVE APPROACH • In this case, a portion of the project with
WITH SOME AGILE uncertainty, complexity, or opportunity for scope
creep is being tackled in an agile way, but the
COMPONENTS remainder of the project is being managed using
predictive approaches.
 • This approach might be used when a particular element is non-
3.1.9 A LARGELY AGILE negotiable or not executable using an agile approach.
APPROACH WITH A • Examples include integrating an external component developed by a
PREDICTIVE COMPONENT different vendor that cannot or will not partner in a collaborative or
incremental way.