Scrum & Kanban Basics

Phase progress0 / 0 completed

Scrum and Kanban are the two most widely adopted Agile frameworks. Both aim to improve team efficiency, transparency, and value delivery, but they take different paths: Scrum uses structured sprints and defined roles to create rhythm and accountability, while Kanban emphasizes visualizing work, limiting work-in-progress (WIP), and optimizing flow. This module introduces the core principles, roles, ceremonies, and artifacts of Scrum, alongside the foundational practices and pull-based workflow of Kanban. By the end, you’ll understand how each framework works, how they differ, and when to use them.

Scrum Basics

An Agile framework that helps teams self-organize, collaborate, and deliver value in time-boxed iterations called sprints (typically 1–4 weeks).

Core Principles:

TransparencyInspectionAdaptation

Kanban Basics

A Lean-inspired Agile framework focused on continuous flow. Work items are visualized on a Kanban board, enabling teams to track progress and manage capacity in real time.

Core Principles:

Visualize WorkflowLimit WIPManage FlowMake Policies Explicit

Scrum vs. Kanban

Dimension	Scrum	Kanban
Structure	Fixed-length sprints (time-boxed)	Continuous flow (no timeboxing)
Roles	Product Owner, Scrum Master, Team	No prescribed roles
Change Philosophy	Scope stable during sprint	Change allowed at any time
Metrics	Velocity (points per sprint)	Cycle time, throughput

Key Takeaway

Scrum and Kanban both help teams deliver value, adapt quickly, and collaborate effectively, but they differ in rhythm and flexibility. Scrum works best for teams that thrive with structure, roles, and iterative cycles, while Kanban suits teams needing lightweight, continuous delivery with minimal disruption to existing processes. Many organizations eventually blend the two into Scrumban—using Scrum’s cadence with Kanban’s WIP limits—for a flexible hybrid approach.