Hybrid Architectures

Three Principled Mergers

Hybrid A: "Governed Agile"

For: Regulated industries, contractual delivery (medical devices, automotive, maritime OT, defense)

PRINCE2 stages containing Scrum Sprints. V-Model test levels automated as CI/CD pipeline. Design Thinking discovery upfront.

Hybrid B: "Discovery-Driven Flow"

For: Product teams, SaaS, startups

Design Thinking discovery track running parallel to Kanban delivery track. DevOps CI/CD. No Sprints — continuous pull. Retrospectives decoupled from delivery cadence.

Hybrid C: "Scaled Governed Flow"

For: Enterprises managing mixed portfolios

Portfolio level on Kanban with PRINCE2 Business Case governance. Program level on SAFe PI cadence. Team level: each team chooses Scrum or Kanban. Shared DevOps platform underneath.

Five Design Principles

1. The Compatibility Rule — check VP binding compatibility before merging
2. The Granularity Principle — different VPs can bind at different organizational levels
3. Start from the Platform — don't modify one framework; compose from the functional slots
4. Automate the Right Arm — V-Model quality structure + DevOps automation = best of both
5. Separate Discovery from Delivery — different activities need different rhythms

The full analysis with binding tables is in Eight Frameworks Decomposed.