The case for Scrum vs Kanban

It has been great working closer with some of the teams and learning and seeing some of your challenges!

We are aware that some of your teams are following scrum whilst others use kanban.  One of the key focus areas which Jacqui and Andre set for this PI, was to become more predictable and deliver what we have committed to. (whatever that commitment might be).

As such we wanted to dive a little bit deeper into the use and advantages of scrum and kanban and advise on what we think would be better for your teams to use.

Comparative Analysis of Scrum vs. Kanban in Agile Methodology

1. Defining Scrum and Kanban:

Scrum:
– A time-boxed, iterative approach where work is segmented into Sprints (typically 2-4 weeks).
– Teams have predefined roles: Product Owner, Scrum Master, and Development Team.
– Uses artifacts like the Product Backlog, Sprint Backlog, and Increments.

Kanban:
– A flow-based approach, where work items are pulled from a backlog and moved to ‘done’ based on capacity.
– No predefined roles; anyone can make process updates.
– Uses a visual board to track the status of work items.

2. Benefits of Each Framework

Scrum:
– Predictability: With fixed-length sprints, stakeholders have a clear view of when new features might be delivered.
– Collaboration: Daily stand-ups and sprint reviews encourage communication.
– Feedback Loop: Regular sprint reviews and retrospectives allow teams to constantly improve.

Kanban:
– Flexibility: No fixed iterations; changes can be introduced at any point.
– Visibility: The Kanban board offers a clear visualization of work and bottlenecks.
– Continuous Delivery: Ideally suited for operations where continuous delivery is beneficial.

3. Disadvantages of Each Framework:

Scrum
– Rigidity: The sprint’s duration and goals are fixed, making it less adaptive to immediate change.
– Overhead: Scrum ceremonies and role definitions can introduce overhead.

Kanban:
– Lack of Structure: Without time-bound iterations, there can be less predictability for stakeholders.
– Potential for Stagnation: Without sprint deadlines, teams might lack the urgency to complete work.

When choosing between Scrum and Kanban, or any methodology for that matter, it’s essential to consider various factors beyond just their pros and cons. Here are some additional considerations to guide your decision:

1. Nature of the Project:

– Complexity: Scrum is often preferred for complex projects where frequent inspection and adaptation are crucial.
– Urgency: For projects where changes and updates are constant and immediate, like in customer support or crisis management, Kanban might be more appropriate because of its flexibility.

2. Team Dynamics:-

Experience with Agile: Scrum often requires a higher level of understanding and discipline due to its ceremonies and roles. Teams new to Agile might find Kanban’s simplicity easier to adopt initially.
– Size of the Team: Larger teams might benefit from the structure of Scrum, while smaller teams might find Kanban’s flexibility more fitting.

3. Stakeholder Involvement:

– Scrum provides regular intervals (like Sprint Reviews) for stakeholder feedback, ensuring that the development aligns with business objectives.
– With Kanban, stakeholder engagement isn’t structured, so teams might need to create separate mechanisms to ensure stakeholder input.

4. Rate of Change:
– For environments where priorities shift rapidly, the flexibility of Kanban is often preferred.
– Scrum, with its fixed sprints, can still accommodate change, but the changes typically take effect in the next sprint.

5. End Goals:

– If your primary goal is to have a potentially shippable product at the end of each iteration, Scrum is designed for that.
– If the focus is more on continuous flow and handling different priorities seamlessly, Kanban might be the way to go.

We really believe that Scrum would be better for moving us towards the goals of being more predictable and learning to deliver what we said we would. However, in some teams such as ACM which need to respond to urgent production issues Kanban may be a better fit.

Takunda and I will be setting up biweekly lean coffee dates with you where we can discuss and help you implement some of these tools.

Items on the Agenda so far:

• • The case for Scrum
  • Estimation pitfalls and estimation checklists
  • Definition of Done
  • Definition of Ready