Development Approach Selection: Impactful Decisions for Project Success
PMBOK v8 Definition
Development approach selection refers to the process of determining the most appropriate life cycle (predictive, adaptive/agile, or hybrid) for a project based on organizational variables, project characteristics, and team capabilities. As stated in PMBOK v8, this decision involves identifying the types of processes and activities that should be performed, and adjusting attributes of activities, phases, or processes. The choice of development approach is one of the most impactful decisions a project team makes, alongside selecting tools or vendors.
Why It Matters for the Exam
This concept appears frequently on the PMI exam in situational questions where you must recommend the best development approach based on given project characteristics. It is tested in both the "Development Approach and Life Cycle" domain and across multiple knowledge areas, particularly in questions about tailoring, team performance, and organizational influences. Expect to see it in scenario-based questions asking which approach fits specific constraints.
Key Points to Remember (for the exam)
- Main Organizational Variables: Structure, culture, capability, project team size, and location influence development approach selection
- Team Skills Requirement: Adaptive/agile approaches benefit from teams with strong communication, collaboration, and problem-solving skills
- Interdependency Factor: Reliance on other projects, departments, or functions for decisions, components, or resources may favor iterative approaches
- Coordination Type: Predictive projects benefit from centralized coordination; agile projects benefit from decentralized coordination where teams self-organize and self-manage
- Life Cycle Flexibility: The project life cycle should be flexible enough to meet target objectives while protecting and enhancing value proposition
- Common Confusion: Confusing "development approach" with "project life cycle" – the approach is selected (predictive, adaptive, hybrid), while the life cycle contains the phases and processes
- Key Decision Factors: Team cohesiveness, skill improvements, reduced staff turnover, and increased team performance are indicators of effective team development that influence approach selection
Typical PMI Exam Example
A project has high uncertainty, requires frequent customer feedback, and the team has strong collaboration skills. The organization has a flat structure with self-managing teams. Question: Which development approach is most appropriate? Answer: Adaptive/agile approach, because the organizational structure supports decentralized coordination and the team has the required communication skills.
PMI Exam Traps
-
Trap: Assuming predictive approaches always require centralized coordination
-
Reality: Some projects with centralized coordination can benefit from hybrid or mixed coordination, including self-organized teams for portions of the work
-
Trap: Thinking development approach selection is solely based on project complexity
-
Reality: Organizational variables (structure, culture, capability, team size, location) are equally important decision factors
-
Trap: Confusing team lunch decisions (low impact) with development approach decisions (high impact)
-
Reality: The PMBOK explicitly contrasts minor decisions with impactful ones like development approach, tool selection, and vendor selection
-
Trap: Believing one development approach fits all project phases
-
Reality: The project life cycle should be flexible, allowing selection of a mix of approaches for different phases
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Project Life Cycle | Determined by approach | The life cycle must be flexible to accommodate the selected development approach |
| Organizational Structure | Influences approach selection | Flat structures favor agile; hierarchical structures favor predictive |
| Team Performance | Indicator of effectiveness | Skill improvements and team cohesiveness validate approach selection |
| Tailoring | Applied through approach selection | Adjusting processes and activities based on approach choice is a tailoring activity |
| Value Proposition | Protected by approach choice | The selected approach should enhance the project's value proposition |
Quick Review Questions
-
A project has high interdependencies with other departments. Which development approach might be most appropriate, and why?
-
What are the four indicators used to evaluate a team's effectiveness according to PMBOK v8?
-
Your organization has a hierarchical structure with centralized decision-making. The project team is large and geographically distributed. Which development approach is likely most suitable?
-
A project team has strong communication, collaboration, and problem-solving skills. What type of development approach would benefit most from these capabilities?
-
True or False: Once a development approach is selected, it cannot be changed during the project life cycle.
PMBOK v8 Reference
Section 4.3.3 – Organization (Organizational variables influencing development approach selection) Section 4.3 – Development Approach and Life Cycle (Life cycle flexibility and approach selection)