Scrumban

1,285 views
817 views

Published on

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,285
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
39
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Scrumban

  1. 1. Scrumban EPAM systems Pavel Kamyshov
  2. 2. Common issues • Unsteady workload during a sprint (late releases => overtimes/low quality) • Changing sprint scope during an iteration (huge planning obstacle) • Teams over 9 people (extended communication)
  3. 3. Scrum • Iterative and incremental framework • Two weeks sprints. Plus stand-ups and retrospectives. Continuous integration. • Sprint starts from planning and estimations. Story workflow: analysis => development => testing => demo
  4. 4. Scrum workflow • Scrum is an iterative and incremental agile approach for managing software projects. • Scrum methodology consists of a series of sprints(iterations) usually lasting two weeks or so. With every day scrum stand ups and regular retrospectives. In the end of each sprint business gets working software. • Sprint starts from planning and estimations. Story goes through analysis, development, testing and demonstrating to the client finally.
  5. 5. Scrum Disadvantages • Static sprints • Too many stories are created/analyzed simultaneously • “This is not in scope of the story” (Agile common problem)
  6. 6. Kanban • Continuous development. No sprints. • Visualized workflow: ToDo, In Progress(Development), Testing, Deploying. • WIP (work in progress) for every column
  7. 7. Kanban workflow • Scrum is an iterative and incremental agile approach for managing software projects. • Scrum methodology consists of a series of sprints(iterations) usually lasting two weeks or so. With every day scrum stand ups and regular retrospectives. In the end of each sprint business gets working software. • Sprint starts from planning and estimations. Story goes through analysis, development, testing and demonstrating to the client finally.
  8. 8. Kanban Disadvantages • Communication problems when 5 people work on same story • Ineffective resource consumption • No defined time for stabilization/regression
  9. 9. Scrumban • What the best we could take from both worlds?
  10. 10. Start your Scrumban • Continuous development. But still defined sprints. • Visualized workflow: ToDo, In Progress(Development), Testing, Deploying. • Avoid assigning all stories to people in the beginning of the sprint
  11. 11. Scrum vs Scrumban
  12. 12. Kanban vs Scrumban
  13. 13. What to do first? • Stop assigning people to all the stories • Do NOT refuse sprints and stand-ups till the very end! • Retrospectives – always go forward • Don’t walk smack into Scrum/Kanban disadvantages
  14. 14. Solved problems • Idle time of team members significantly reduced • No overloads • Sprint scope can be changed any day
  15. 15. Questions?
  16. 16. Sources and contacts • Sources of the presentation: http://habrahabr.ru/company/softline/blog/140737/ http://www.slideshare.net/frndsavita/scrumban-15943841 http://scrum.org.ua/wp-content/uploads/2008/12/scrum_xp- from-the-trenches-rus-final.pdf • Skype: pavelkamyshov

×