The Agile Scrum Framework Vs Kanban Model

1. By Venkat SR Godugu

2. Lean and Agile Methods
Lean and Agile got married and got 3 kids as Scrum, XP and Kanban
Lean Agile
Kanban
Scrum
XP
Scrum: Release planning,
sprint and iteration planning,
daily scrum, sprint demo, etc
XP: TDD, Automated
testing, continuous
integration, Refractory, etc
Kanban: Limit work in
progress, Optimize the Flow,
and make it visible

3. Scrum Framework
Scrum (n): Scrum was first defined as "a flexible, holistic product development
strategy where a development team works as a unit to reach a common goal" as opposed
to a "traditional, sequential approach" by Hirotaka Takeuchi and Ikujiro Nonaka in
the "New Product Development Game" in 1986 .
Scrum Roles: Product Owner (sets product vision & priorities), Team(implements the
product) and Scrum Master (removes impediments and provides process
leadership)
Ceremonies: Sprint Planning, Sprint review, Sprint Retrospective and Daily Scrum
Artefacts: Product Backlog, Sprint Backlog and Burn down Chart.
Daily scrum: It’s 15 min time boxedLean Agile 3 questions
stand-up to answer
1.What did you do yesterday
2.What will you do today?
3.What obstacles are in your way?
Product backlog: A prioritized list of high-level requirements.
Sprint backlog: A prioritized list of tasks to be completed during the sprint.
Sprint: A time period (1–4 weeks) in which development occurs on a set of backlog
items that the team has committed to. Also commonly referred to as a Time-box or
iteration.
Sprint burn down chart: Daily progress for a Sprint over the sprint's length.
Release burn down chart: Sprint level progress of completed product backlog items
in the Product Backlog.

4. Kanban Method
Kanban: The name 'Kanban' originates from Japanese and translates roughly as "signal
card". The Kanban method as formulated by David J. Anderson
Kanban can be divided into two parts:
1. Kanban– A visual process management system that tells what to produce, when to
produce it and how much to produce.
2. The Kanban method – An approach to incremental, evolutionary process
improvement for organizations.
1. Visualize the workflow
o Split the work into pieces, write each item on a card and put on the wall
Lean Agile
o Use named columns to illustrate where each item is in the workflow.
2. Limit WIP (work in progress) – assign explicit limits to how many items may be in
progress at each workflow state.
3. Measure the lead time (average time to complete one item, or “cycle
time”), optimize the process to make lead time as small and predictable as possible.
4. Make policies explicit: Until the mechanism of a process is made explicit it is often
hard or impossible to hold a discussion about improving it.
5. Implement feedback loops - Collaboration to review flow of work, demand versus
capability measures, metrics and indicators coupled with notable events is vital to
enabling evolutionary change.
6. Improve collaboratively, evolve experimentally (using models & the scientific
method)

5. Scrum VS Kanban
Item
Scrum
Kanban
Board / Artefacts
Board, Backlogs, Burn-downs
Board only
Ceremonies
Daily scrum, Sprint planning, Sprint
review, Sprint retrospective
Daily scrum, review/retrospective on
set frequency and planning ongoing
Iterations
Sprints
Continuous flow
Estimation
Yes
No - Similar Size
Teams
Must be cross-functional
Roles
Product Owner, Scrum Master, Team
Team + needed roles
Teamwork
Collaborative as needed by task
Swarming to achieve goals
WIP
Controlled by sprint content
Controlled by workflow state
Changes
Should wait for the next sprint
Added as needed on the board (to do)
Product Backlog
List of prioritized and estimated stories
Just in time cards
Impediments
dealt with immediately
Avoided
Lean AgileCan be specialized