• ES Español (Latinoamérica)
• EN English

5.4. Development Approach and Life Cycle (DL)

This performance domain covers the activities and functions associated with selecting, defining, and managing the development approach and the project life cycle. PMBoK 7th edition treats the choice of development approach as a deliberate, context-driven decision rather than a default.

Knowledge Area (KA)	Core Tier1	Core Tier2
5.4.1 Kickoff and Closure Activities	1	1
5.4.2 Development Approach Selection	Elective
5.4.3 Predictive Approach	Elective
5.4.4 Adaptive Approach	Elective
5.4.5 Hybrid Approach	Elective
5.4.6 Project Phase Structure	Elective
5.4.7 Tailoring the Development Approach	Elective

5.4.1. DL/Kickoff and Closure Activities  (Core Tier1: 1 hr, Core Tier2: 1 hr) ↑ Back to top

Key activities at the start and end of the project and its phases. Covers project kickoff, phase transitions, and formal closure activities.
Topics:
Core

• Project kickoff: aligning team and stakeholders on objectives, approach, and working agreements
• Phase transition activities: reviews, approvals, and handoffs between phases
• Project closure: final deliverable acceptance, lessons learned, and team release
• Integrating lessons learned from closure into organizational knowledge assets

Learning Outcomes:
Core:

1. Conduct an effective project kickoff that aligns team and stakeholders on goals and approach [Usage]
2. Execute project closure activities including final acceptance and lessons learned archiving [Usage]
3. Design a comprehensive project closure checklist ensuring all administrative, contractual, and knowledge capture obligations are met [Assessment]

5.4.2. DL/Development Approach Selection ↑ Back to top

Selecting the most appropriate development approach - predictive, adaptive, or hybrid - based on project characteristics, organizational factors, and stakeholder needs.
Topics:
Core

• Overview of development approaches: predictive, iterative, incremental, adaptive, and hybrid
• Selection criteria: degree of uncertainty, rate of change, stakeholder involvement, and team capability
• Organizational factors influencing approach selection: culture, standards, and governance
• Evolving and adjusting the development approach as the project progresses

Learning Outcomes:
Core:

1. Select an appropriate development approach for a project based on defined selection criteria [Usage]
2. Justify the selected development approach given organizational and project-specific factors [Assessment]
3. Evaluate the alignment between a chosen development approach and the project's uncertainty level, team capability, and stakeholder engagement requirements [Assessment]

5.4.3. DL/Predictive Approach ↑ Back to top

Understanding when and how to apply a predictive (plan-driven) approach. Covers sequential phases, detailed upfront planning, and change management in predictive environments.
Topics:
Core

• Characteristics of predictive approach: sequential phases, fixed scope, and detailed upfront planning
• Conditions favoring predictive approach: stable requirements, low uncertainty, regulatory constraints
• Managing change in predictive environments: formal change control and baseline management
• Limitations of predictive approach in complex and uncertain environments

Learning Outcomes:
Core:

1. Describe the characteristics and appropriate use cases of a predictive development approach [Familiarity]
2. Apply predictive approach practices to plan and manage a project with stable requirements [Usage]
3. Evaluate when a predictive approach is or is not suitable for a given project context [Assessment]

5.4.4. DL/Adaptive Approach ↑ Back to top

Understanding when and how to apply adaptive (agile) approaches. Covers iterative and incremental delivery, backlog management, and empirical process control.
Topics:
Core

• Characteristics of adaptive approach: iterative delivery, evolving requirements, and empirical control
• Scrum and Kanban as representative adaptive frameworks
• Product backlog management: prioritization, refinement, and sprint planning
• Scaling adaptive approaches for large teams: SAFe, LeSS, and disciplined agile

Learning Outcomes:
Core:

1. Describe the characteristics and appropriate use cases of adaptive development approaches [Familiarity]
2. Apply adaptive approach practices including backlog management and iterative delivery [Usage]
3. Select an appropriate scaling framework for an adaptive approach in a large-team context [Assessment]

5.4.5. DL/Hybrid Approach ↑ Back to top

Combining predictive and adaptive elements to create a tailored development approach. Hybrid approaches acknowledge that few projects are purely predictive or purely adaptive.
Topics:
Core

• Rationale for hybrid approaches: mixing predictive stability with adaptive flexibility
• Common hybrid patterns: predictive planning with agile delivery, rolling wave with fixed milestones
• Governance challenges in hybrid approaches: reporting, metrics, and decision authority
• Managing the transition between predictive and adaptive phases within a hybrid life cycle

Learning Outcomes:
Core:

1. Design a hybrid approach combining predictive and adaptive elements for a given project context [Usage]
2. Evaluate the governance implications of a hybrid development approach [Assessment]
3. Justify the selection of a hybrid approach over a purely predictive or purely adaptive alternative [Assessment]

5.4.6. DL/Project Phase Structure ↑ Back to top

Defining the phase structure of the project life cycle, including phase sequencing, gate reviews, and the relationship between phases and the development approach.
Topics:
Core

• Defining project phases: sequential, overlapping, and iterative phase structures
• Phase gate reviews: decision criteria, governance, and go/no-go decisions
• Aligning phase structure with the selected development approach
• Defining exit criteria and deliverable acceptance standards for each project phase

Learning Outcomes:
Core:

1. Define an appropriate phase structure and gate review criteria for a given project [Usage]
2. Align the project phase structure with the selected development approach [Assessment]
3. Design a phase gate framework with clear entry and exit criteria appropriate to the project's risk profile [Assessment]

5.4.7. DL/Tailoring the Development Approach ↑ Back to top

Systematically tailoring the development approach and life cycle to the specific needs of the project. Tailoring is a deliberate, ongoing activity that balances organizational standards with project context.
Topics:
Core

• Tailoring process: assess context, select approach, customize, and continuously adjust
• Constraints on tailoring: regulatory requirements, organizational standards, and customer expectations
• Documenting tailoring decisions and rationale for governance and audit purposes
• Reviewing and refining tailoring decisions at project milestones based on performance evidence

Learning Outcomes:
Core:

1. Apply a tailoring process to customize the development approach for a specific project [Usage]
2. Justify tailoring decisions within organizational and regulatory constraints [Assessment]
3. Evaluate the effectiveness of tailoring decisions at project milestones and propose refinements [Assessment]