1. ~ Savita Pahuja
CSM, CSPO, PSM I
CSC India pvt Ltd

2. Scrum
Scrum is an iterative and incremental agile software
development method for managing software projects
and products or application development.
Scrum focuses on project management where it is
difficult to plan ahead.
The Scrum methodology consists of a series of “sprints”
typically lasting two to four weeks, each delivering
some working, potentially shippable software.

3. Kanban
Kanban is a scheduling system that helps determine
what to produce, when to produce it, and how much to
produce.
Kanban is a method with an emphasis on just-in-time
delivery (as when production support ticket arise, solve
at that moment) while not overloading the software
developers. It emphasizes that developers pull work
from a queue, and the process, from definition of a task
to its delivery to the customer.

4. Workflow of Scrum
Sprint Cycle

5. Workflow of kanban
No “sprint end” – Continuous flow

6. Scrumban = Scrum + Kanban
Scrumban is a software production model based on
Scrum and Kanban.
Use the communication and role benefits of
Scrum to be agile.
Use the process improvement of Kanban to
allow the team to continually improve their
process.

7. maintenance projects
 event driven work
help-desk/support
hardening/packaging phases
projects with frequent and unexpected
user stories or programming errors
When to consider Scrumban

8. Sprint teams focused on new product
development
work preceding sprint development (backlog,
R&D)
work following sprint development (system
testing, packaging and deployment)
If Scrum is challenged by workflow issues,
resources and processes
To manage improvement communities
during/after Scrum roll-out

9. Scrumban Backlog
avoid creating/analyzing too many stories
(requirements/defects) - reduce waste
 assure the necessary level of analysis before
starting development
 the backlog should be event-driven with an
order point
 prioritization-on-demand - the ideal work
planning process should always provide the team
with best thing to work on next, no more and no
less

10. Scrumban Board

11. Scrum vs Scrumban

12. Kanban Scrumban
Roles No prescribed role Team + needed roles
Daily scrum
meeting
No meeting To make sure continuous work on
requirements and reduce idle time
of team members.
Sprint
Planning
Meeting
No meeting. Can be done to plan to fill the slots
Review and
Retrospective
Meeting
Not prescribed. Can be done as needed for process
improvement and share learnings.
Work Flow Continuous Same as in Kanban. Just add limit
of slots so that pull process will
become more comfortable.
Kanban vs Scrumban

13. Savita Pahuja
Savita.pahuja@gmail.com
http://www.linkedin.com/in/savitapahuja
13