Embedded Files
1 Day(s)
🎯 LEARNING OBJECTIVES
After completing this lesson, learners will be able to:
Explain Kanban and Scrumban and their roles in Agile project and workflow management.
Differentiate Kanban, Scrum, and Scrumban based on planning, workflow, roles, and delivery cadence.
Design a Kanban board with workflow stages, work items, and explicit policies.
Apply Work in Progress (WIP) limits to reduce multitasking, expose bottlenecks, and improve flow.
Implement Scrumban practices by combining suitable Scrum planning and review activities with Kanban flow management.
Measure workflow performance using lead time, cycle time, throughput, and WIP.
Select the appropriate approach based on workload predictability, team needs, and delivery objectives.
Improve workflow continuously by analyzing bottlenecks, managing blockers, and adapting working policies.
🧠 PREREQUISITES
Agile Fundamentals: Basic understanding of Agile values, principles, and iterative delivery.
Scrum Fundamentals: Familiarity with sprints, backlogs, daily Scrum, and retrospectives.
Workflow Management: Basic understanding of task states, priorities, dependencies, and work assignment.
Team Collaboration: Familiarity with cross-functional teams and shared delivery responsibilities.
Basic Metrics: Awareness of delivery time, work completion, and team capacity.
Kanban Framework
1.Introduction To KANBAN
1.Introduction To KANBAN
Developed by Toyota, means the board
Management focus
A visual workflow management method focused on continuous delivery, work-in-progress (WIP) limits, and flow efficiency. Originated from Lean Manufacturing (Toyota)
2.Core KANBAN Practices:
2.Core KANBAN Practices:
Visualize the workflow (Kanban board: To Do → Doing → Done).
Limit Work in Progress (WIP).
Manage flow (optimize time from start to finish).
Make policies explicit.
Implement feedback loops (daily standups, metrics).
Improve collaboratively (based on data & experiments).
3.Kanban Vs Scrum:
3.Kanban Vs Scrum:
It's Continuous flow instead of Fixed Sprints
No fixed roles instead of cross functional team
Controlled via WIP limits instead of sprint control
On-demand instead of release and sprint planning
Changes allowed anytime instead of change freezing during sprint
Lead time, Cycle time, Throughput instead of Velocity and burndown
4.When To Use KANBAN?
4.When To Use KANBAN?
With the Support team
Frequent changes
Unpredictable work
Need for flexible delivery
So enterprises can adapt Kanban in support of SQUADs and mission-critical SQUADs.
5.Scrumban
5.Scrumban
Mix between Scrum and Kanban
Causes additional overhead on the development team, as it increases deployment overheads
Scrumban = Scrum structure + Kanban flexibility — Ideal for teams needing agility without losing predictability.
Uses Scrum structure (optional sprints), with Kanban flow.
May retain Scrum roles (PO, SM, Devs).
Combines backlog grooming + Kanban pull.
WIP Limits Used, but may be flexible.
Meetings: Can keep Scrum ceremonies (daily, retro, review).
Best For:
Government sectors that require continuous delivery for the customer
Core team that all SQUADs have dependencies on
Managed Product Support team, which should release batches regularly
Teams transitioning from Scrum to Kanban.
Dr. Ghoniem Lawaty
Tech Evangelist
Page updated
Google Sites
Report abuse