Certified Associate in Project Management (CAPM) Hybrid Approaches and Tailoring Syllabus

Hybrid Approaches and Tailoring syllabus — full chapter and topic list

Expand any chapter to see its topics and sub-topics. This is the whole examinable outline for Hybrid Approaches and Tailoring in Certified Associate in Project Management (CAPM), not a summary of it.

1. 1

   Selecting and Tailoring the Approach

   4 topics

   • Factors driving approach selection
     • Requirement stability and degree of change
     • Risk, complexity, and delivery cadence
     • Organizational culture and team experience
   • Suitability assessment tools and filters
   • Tailoring processes, life cycles, and artifacts
   • Continuous tailoring throughout the project
2. 2

   Designing Hybrid Models

   4 topics

   • Combining predictive and adaptive elements
     • Predictive planning with agile execution
     • Agile within predictive phase gates
   • Phased hybrid: sequencing predictive and agile phases
   • Choosing artifacts and ceremonies for a hybrid team
   • Governance and reporting in hybrid environments
3. 3

   Implementing and Sustaining Hybrid Delivery

   5 topics

   • Integrating teams using different approaches
   • Aligning metrics across predictive and agile work
   • Managing dependencies between work streams
   • Change management within a hybrid context
   • Lessons learned and adapting the hybrid model

Hybrid Approaches and Tailoring flashcards for Certified Associate in Project Management (CAPM)

24 of 51 cards from the Hybrid Approaches and Tailoring deck — real questions with worked answers.

1. In project management, what does "tailoring" mean?

   Deliberately adapting the approach, governance, processes, life cycle, tools, and artifacts to fit the unique context of a specific project, organization, and environment rather than applying a method by rote.

2. What is a "hybrid" project approach?

   An approach that intentionally combines elements of both predictive (plan-driven) and adaptive (agile/iterative) methods within the same project to suit its needs.

3. Name the three broad categories on the development-approach continuum that hybrids draw from.

   Predictive (plan-driven/waterfall), iterative/incremental, and adaptive (agile). Hybrids blend predictive with adaptive/iterative.

4. List the main factors that drive the selection of a development approach.

   Product/deliverable factors (degree of innovation, requirements certainty, ease of change), project factors (constraints, delivery options, size, risk), and organizational factors (structure, culture, capability, team size and location).

5. Which product characteristics push a project toward an adaptive (agile) approach?

   High uncertainty in requirements, high rate of expected change, high innovation/novelty, and the ability to deliver in increments where early feedback adds value.

6. Which product characteristics push a project toward a predictive approach?

   Well-understood, stable requirements; low expected change; clear final product; need for upfront definition; and deliverables that are hard or costly to change once built.

7. How does requirements stability influence approach selection?

   Stable, clear requirements favor predictive planning; volatile or emerging requirements favor adaptive approaches that embrace change through iterations.

8. How does the cost or difficulty of change influence approach choice?

   When changes are cheap and easy to incorporate, adaptive approaches work well; when changes are expensive or physically hard to reverse (e.g., construction), predictive planning is favored.

9. What organizational factors affect whether a team can use an adaptive approach?

   Organizational culture, structure (functional vs. projectized), governance maturity, team co-location/distribution, team size, and the team's experience with agile.

10. What is a suitability assessment in the context of choosing an approach?

    A structured evaluation of project, culture, and team dimensions to recommend whether a predictive, hybrid, or agile approach best fits the situation.

11. Name the three main assessment dimensions in PMI's Agile Suitability Filter model.

    Culture, team, and project.

12. Under the Agile Suitability Filter, which culture factors are assessed?

    Buy-in for the approach (executive support), trust in the team, and decision-making empowerment given to the team.

13. Under the Agile Suitability Filter, which team factors are assessed?

    Team size, experience levels, and access to the customer/business representative.

14. Under the Agile Suitability Filter, which project factors are assessed?

    Likelihood/rate of change, criticality of the product (potential for incremental delivery), and the relative importance of incremental delivery.

15. How is the Agile Suitability Filter result typically visualized?

    As a radar (spider) chart; scores near the center suggest agile suitability, scores near the outer edge suggest predictive, and mixed results suggest a hybrid approach.

16. What is the relationship between tailoring and a project's life cycle?

    Tailoring selects and shapes the life cycle (predictive, iterative, incremental, agile, or hybrid) and its phases so the sequence of work fits the project's delivery needs.

17. What are the four common elements that get tailored on a project?

    Life cycle and development approach selection, processes, engagement (people/roles), and tools, methods, and artifacts.

18. Why is tailoring considered a continuous activity rather than a one-time decision?

    Because project conditions, risks, and learnings change over time, so the approach, processes, and artifacts should be reviewed and adjusted throughout the project, not just at initiation.

19. At what points during a project should tailoring be revisited?

    At initiation, at phase gates/transitions, during retrospectives, when major changes or risks emerge, and whenever performance feedback indicates the current approach is not working.

20. What is "continuous improvement" tailoring driven by within an agile/hybrid project?

    Regular retrospectives and lessons learned, where the team inspects its process and adapts ceremonies, artifacts, and ways of working incrementally.

21. Define a "phased hybrid" approach.

    A project structured so that some phases use a predictive approach and others use an adaptive/agile approach, sequenced one after another (e.g., predictive planning then agile build).

22. Give a typical example of sequencing in a phased hybrid project.

    Use predictive methods for early phases like feasibility, requirements, and design, then switch to agile/iterative delivery for development and testing, and possibly predictive again for deployment.

23. What is the difference between a phased hybrid and a combined (concurrent) hybrid?

    A phased hybrid runs predictive and agile in separate sequential phases; a combined hybrid blends predictive and adaptive elements simultaneously within the same phase or across parallel work streams.

24. In a hybrid where agile is used for the product but predictive for procurement, why split it that way?

    The uncertain, evolving product benefits from iterative agile delivery, while contracts/procurement need fixed, plan-driven controls—so each part uses the approach best suited to its uncertainty and change profile.

See more Hybrid Approaches and Tailoring flashcards →

Planning Hybrid Approaches and Tailoring for Certified Associate in Project Management (CAPM)

Hybrid Approaches and Tailoring (Certified Associate in Project Management (CAPM)) FAQ