Hybrid Development Approach

Definition

A hybrid approach combines elements of predictive and adaptive development. The high-level roadmap and governance structure may be predictive, while component or feature delivery is executed in adaptive sprints. Hybrid is useful when some parts of a project have stable, well-defined requirements while others are exploratory or uncertain. Tailoring determines which elements are predictive and which are adaptive.

Exam angle

  • Integration overhead: hybrid requires extra effort to integrate adaptive subteam outputs into a predictive reporting baseline — this is a real risk on the exam
  • Tailoring justification: choosing hybrid requires explaining which project elements justify each approach — not a default choice
  • Governance alignment: hybrid projects often need dual reporting: sprint velocity for agile components + EVM or milestone reports for predictive components

My notes