1. SCRUM + KANBAN
SCRUMBAN
Work-in-progress
limits
Retrospective
meeting
Time Limit
2-4weeks
Conducing daily
stand-ups
Demonstration
Pair programming
Just-in-time
planning
limited
stories
Team work
Focus on story
KAIZEN
continuous improvement
For better workflow
When SCRUMBAN should introduced?
When developer team have worked with
SCRUM and trying to improve their work.
SCRUMBAN BOARD
DIAGRAM
FEATURES
ADVANTAGES
Goodness of SCRUM and KANBAN
Continuous flow of stories
.SCRUMBAN can’t improve a bad team
to good, defiantly a good team to better.
Lean system of SCRUM
Jamal Mostafa Eahsan 2014-3-60-056
Md. Afser Uddin 2015-2-60-083
Nusrat Binte Islam 2014-3-60-033
GROUP MEMBERS
INTRODUCTION
SCRUMBANwas design for more
Mature agile terms , for
Unpredictable Environment
where plans and requirements
Constantly shift , supportingexisting
Product rather then creating new one.