Up

1. What is Scrumban?

• Scrum: An agile framework which comprises principles and practices that help teams to deliver new products as soon as possible in continual improvement and with rapid adaptation to changes.
• Kanban: A process management method that builds on the experience of other agile methods. The main objective of Kanban is waste and delay elimination, that has a positive effect on workflow optimization.
• Scrumban: A composite of Scrum and Kanban methods, as it contains basic properties of Scrum and flexibility of Kanban.

Up

2. How Does Scrumban Work?

• Scrum: Project organized in short iterations, during which the team works to add incremental value to the end project. It does not encourage teams to make changes during the course of the sprint.
• Kanban: Projects run on need-based iterations during which the team produces incremental value to the end product. Change is recommended if the needs of the project demand it.
• Scrumban: Continuous work with planning on demand and detached releases once the product is ready. Process is slightly constrained.

Up

3. Why Scrumban?

The Scrumban method combines the best elements from Scrum and Kanban. The flow-based methods of Kanban add process improvement, visualization, and more value metrics to the basic structure of Scrum.

Up

4. What is Scrumban Fit For?

• Scrum: Enterprise maturity for teams working on product or especially project which is longer than a year
• Kanban: Support and maintenance teams, continuous product manufacturing
• Scrumban: Startups, fast-paced projects, continuous product manufacturing.

Up

5. Scrum, Kanban, and Scrumban Compared

Roles

• Scrum: Product owner, Scrum master, Cross-functional team
• Kanban: Cross-functional team
• Scrumban: Cross-functional team.

Iterations

• Scrum: Sprints: 1-4 weeks iterations planned and run one at a time
• Kanban: Continuous work. Planned on the need basis and ended once added substantial value to the product
• Scrumban: Continuous work. Planned on the need basis and released once the product is ready.

Task

• Scrum: One task should fit within a single Sprint. Usually split if exceeding 12 hrs
• Kanban: Any size but clear goal for a team member to complete
• Scrumban: Any size but clear goal for a team member to complete.

Estimation

• Scrum: Done before every Sprint, either in hours or Story Points
• Kanban: Optional. If any, done in hours or broad size metrics, such as S, M, and L
• Scrumban: Optional. If any, measured against the average cycle time.

Scope Limits

• Scrum: Sprints limit the amount of work the team is going to do
• Kanban: Work in Progress (WIP) limit the number of tasks the team can work on at any given point
• Scrumban: Work in Progress (WIP) limit the number of tasks the team can work on at any given point.

Meetings

• Scrum: Sprint planning, daily scrum, sprint review, and sprint retrospective
• Kanban: Avoidable. If any: planning session, daily stand up, iteration review, and retrospective
• Scrumban: Avoidable. If any: planning session, daily stand up, and Kaizen.

Up

6. Key Terms

Scrum

• Product backlog
• Sprint backlog
• Story point
• User story
• Burndown chart
• Team velocity

Kanban

• Kanban Board
• Planning trigger
• Bottleneck
• Lead time
• Cycle time
• CFD
• Swim lane

Scrumban

• Average cycle time
• Triage trigger
• Triage
• Feature freeze
• Planning buckets
• Planning Trigger

Up