Categories
Uncategorised

Scrum + Waterfall = Scrummerfall: Bridging Structure and Flexibility

Scrum + Waterfall = Scrummerfall: Bridging Structure and Flexibility

Waterfall approach

| he Waterfall approach is a traditional project management methodology that focuses on a linear, step-by-step process. It emphasizes structure, clear roles, accountability, and defined outcomes. With Waterfall, each phase flows into the next, and teams typically operate within a predefined set of rules and objectives. It’s ideal for projects with predictable, repeatable tasks, where clear planning and control are paramount. However, its rigid structure can falter in dynamic, complex environments where change is frequent, and outcomes are uncertain. For example, Waterfall struggles in areas requiring adaptability and quick shifts, such as political, emergent, or highly innovative projects.

Agile framework

In contrast, Scrum is an agile framework that thrives in uncertainty. It focuses on enabling teams, especially those of experts, to solve problems collaboratively. Rather than directing every step, Scrum facilitates the team’s self-organization, supporting innovation and adaptability. It allows for ongoing refinement of tasks based on new insights and changing conditions. Scrum emphasizes continuous improvement through short, iterative cycles (sprints), where teams review, plan, and adjust their approach frequently.

Combining

Combining these two frameworks creates a “Scrummerfall” approach, where the structured governance of Waterfall and the flexibility of Scrum coexist. This hybrid model allows teams to manage emergent tasks through Scrum while maintaining the rigorous controls and deliverables of Waterfall.

Project Plan

Phase / Task Start End % Complete Owner
Task 001 01-Mar 01-Mar 100 AB
Task 002 01-Mar 01-Mar 90 AB
Task 003 01-Mar 01-Mar 50 CD
Task 004 01-Mar 01-Mar 0 EF
Task 005 01-Mar 01-Mar 0 AB
Task 006 01-Mar 01-Mar 0 AB

Routine Meetings

Agenda Who Time
Review last meeting commitments AB 5mins
Item or Deliverable No1 AB 5mins
Item or Deliverable No2 CD 5mins
Item or Deliverable No3 EF 5mins
Item or Deliverable No4 EF 5mins
Item or Deliverable No5 EF 5mins
Review risks, issues, decisions EF 5mins
Actions and tasks for next meeting EF 5mins

A key aspect of Scrummerfall is having a clear “To-Do List” for products or deliverables, much like Scrum’s product backlog. By using tools like Kanban boards or task logs, the team can ensure accountability and track progress without getting lost in a detailed Gantt chart.

Kanban boards

Deliverable / ToDo Not Started In Progress Stuck Complete
Document x
Report x
Item x
Document x
Report x
Item x

Deliverables To Do List

Deliverable / ToDo Author Reviewer Approver Notes / Status
Document AB CD EF Approved dd/mmm
Report AB CD EF Approved dd/mmm
Item AB CD EF Final
Document AB CD EF Final
Report AB CD EF Draft
Item AB CD EF Draft

Governance

Governance in Scrummerfall is achieved through structured meetings. These meetings should have a clear agenda, defined outcomes, and should focus on risks, issues, dependencies, and decisions. Action items and decisions are tracked in logs and serve as a record, not an alternative to conversation.

Project initiation documents (a nod to Waterfall) define the project’s scope and deliverables, while regular updates help teams stay focused on the tasks at hand. By combining both approaches, Scrummerfall ensures that teams maintain flexibility and innovation while staying aligned with overarching goals and timelines.

Structure and flexibility

Scrummerfall is the ideal solution for projects that require both structure and flexibility, where innovation and predictability need to coexist. By adapting to the needs of the project and leveraging the strengths of both methodologies, teams can achieve their goals efficiently and effectively.

#Scrummerfall #ProjectManagement #Agile #Waterfall #Scrum #HybridApproach #Governance #Innovation #Teamwork