Hybrid Methodology

Hybrid methodology blends Agile and traditional project management approaches, recognising that neither approach is ideal for every situation. It allows teams to use the most appropriate practices for different aspects of a project.

Common hybrid patterns:

• Water-Scrum-Fall: Waterfall planning and governance with Agile delivery in the middle
• Agile with milestones: Agile sprints within a milestone-based project framework
• Phased Agile: Traditional phases (initiation, planning) followed by Agile execution
• Selective Agile: Agile for development, traditional for procurement and compliance
• Scaled hybrid: Portfolio-level waterfall with team-level Agile

When hybrid works well:

• Fixed-scope contracts that require Agile delivery flexibility
• Regulated environments needing formal documentation with iterative development
• Organisations transitioning from waterfall to Agile
• Projects with hardware and software components (hardware often suits sequential planning)
• Projects requiring integration with traditionally managed external parties

Hybrid implementation considerations:

• Define which practices come from which methodology and why
• Establish clear governance that bridges both approaches
• Ensure team members understand both methodologies
• Create reporting that satisfies traditional stakeholders (milestones, Gantt) and Agile teams (velocity, burndown)
• Manage the interface between Agile and traditional workstreams

Common challenges:

• Confusion about which practices to follow
• Stakeholders expecting waterfall certainty with Agile flexibility
• Overhead of maintaining two sets of artefacts
• Difficulty measuring progress consistently across methodologies
• Risk of adopting the worst of both rather than the best of each