At COMMpla, the choice between SCRUM and Kanban isn’t a matter of preference but a strategic decision tailored to the unique needs of our diverse teams. With both methodologies in use across our organisation, we have adopted a hybrid approach to ensure each team operates at its best, leveraging the strengths of these frameworks depending on workflow characteristics, task structure, and dependencies.

Why a Mixed Approach?

The work dynamics of our teams vary significantly. For some, tasks flow continuously and are largely independent of one another. For others, projects require structured planning, prioritisation, and collaboration on interconnected deliverables. This diversity naturally lends itself to using both SCRUM and Kanban, each in scenarios where they excel.

At COMMpla, our philosophy has always been rooted in inspect and adapt. Nothing is ever taken for granted—we test, tailor, and verify whether a solution fits the reality in which it’s implemented. Over the years, we’ve experimented with every conceivable option, and currently, we’re finding great value in this hybrid mix of SCRUM and Kanban. That said, we remain open to evolution, knowing that nothing prevents us from revisiting and changing our approach in the future to better suit emerging needs.

Kanban for Continuous and Predictable Workflows

Kanban shines in environments where tasks arrive at a steady pace and are relatively independent. At COMMpla, we use Kanban for teams like Graphic Design and Video Editing, where the workflow is predictable, and tasks are less likely to depend on one another.

For these teams:

• Task Independence: Deliverables, such as graphic designs or video edits, are often atomic, meaning they can be completed without requiring other tasks to be finalised first.
• Steady Input Flow: The influx of tasks is continuous but stable, following a predictable trend.
• Flexibility in Prioritisation: While prioritisation is important, the nature of the work allows for greater adherence to a FIFO (First In, First Out) approach, reducing bottlenecks and maintaining efficiency.

Kanban provides a visual representation of the workflow, enabling these teams to manage their work-in-progress effectively and deliver high-quality outputs without the overhead of formalised sprint planning.

SCRUM for Structured Development Projects

In contrast, our Development Teams benefit from the structured planning and prioritisation that SCRUM offers. Software development often involves tasks with multiple dependencies, requiring a holistic view of the project to ensure successful delivery.

For these teams:

• Dependency Management: Development tasks often rely on each other, making it crucial to plan sprints that account for interdependencies.
• Prioritisation: SCRUM’s sprint planning sessions allow us to prioritise work based on business needs, user stories, and technical requirements, rather than following a strict FIFO model.
• Time-Boxed Deliverables: The iterative nature of sprints ensures progress is measurable and deliverables align with deadlines.

SCRUM fosters collaboration, accountability, and focus, providing a framework that helps our developers handle complex projects effectively.

Inspect, Adapt, and Evolve

Our hybrid approach didn’t come about overnight. It’s the result of a continuous process of experimenting and adapting. We’ve tried purely SCRUM, fully Kanban, and even custom frameworks tailored to specific teams. Each iteration taught us something new, helping us refine our approach.

Currently, this mixed methodology is proving beneficial, but we remain pragmatic. If in the near or distant future a new approach seems more suitable, we won’t hesitate to pivot and adapt once again. This mindset allows us to stay agile—not just in our workflows, but in how we think about managing them.

The Takeaway: Matching the Tool to the Task

Our decision to use SCRUM or Kanban is rooted in the principle of choosing the right tool for the job. By analysing the specific needs of each team, we ensure that workflows are optimised for both efficiency and quality. Kanban provides the flexibility and visual clarity needed for continuous workstreams, while SCRUM brings structure and collaboration to complex, dependency-driven projects.

At COMMpla, this hybrid approach reflects our commitment to empowering our teams with the processes and tools that best suit their work. By doing so, we not only enhance productivity but also foster an environment where our teams can thrive, delivering exceptional results to our clients.