Scrumban

3,256 views

Published on

Published in: Technology
1 Comment
12 Likes
Statistics
Notes
  • Love Scrumban, it's a proper method created by joining instead of throwing out good ideas. I was very surprized when I heard about it for the first time. I needed to take some knowledge (http://kanbantool.com/kanban-library/scrumban is stiil the base for me ;)) and now I love it. Thanks for the slide!
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
3,256
On SlideShare
0
From Embeds
0
Number of Embeds
81
Actions
Shares
0
Downloads
0
Comments
1
Likes
12
Embeds 0
No embeds

No notes for slide

Scrumban

  1. 1. ~ Savita PahujaCSM, CSPO, PSM ICSC India pvt Ltd
  2. 2. ScrumScrum is an iterative and incremental agile softwaredevelopment method for managing software projectsand products or application development.Scrum focuses on project management where it isdifficult to plan ahead.The Scrum methodology consists of a series of “sprints”typically lasting two to four weeks, each deliveringsome working, potentially shippable software.
  3. 3. KanbanKanban is a scheduling system that helps determinewhat to produce, when to produce it, and how much toproduce.Kanban is a method with an emphasis on just-in-timedelivery (as when production support ticket arise, solveat that moment) while not overloading the softwaredevelopers. It emphasizes that developers pull workfrom a queue, and the process, from definition of a taskto its delivery to the customer.
  4. 4. Workflow of ScrumSprint Cycle
  5. 5. Workflow of kanbanNo “sprint end” – Continuous flow
  6. 6. Scrumban = Scrum + KanbanScrumban is a software production model based onScrum and Kanban.Use the communication and role benefits ofScrum to be agile.Use the process improvement of Kanban toallow the team to continually improve theirprocess.
  7. 7. maintenance projects event driven workhelp-desk/supporthardening/packaging phasesprojects with frequent and unexpecteduser stories or programming errorsWhen to consider Scrumban
  8. 8. Sprint teams focused on new productdevelopmentwork preceding sprint development (backlog,R&D)work following sprint development (systemtesting, packaging and deployment)If Scrum is challenged by workflow issues,resources and processesTo manage improvement communitiesduring/after Scrum roll-out
  9. 9. Scrumban Backlogavoid creating/analyzing too many stories(requirements/defects) - reduce waste assure the necessary level of analysis beforestarting development the backlog should be event-driven with anorder point prioritization-on-demand - the ideal workplanning process should always provide the teamwith best thing to work on next, no more and noless
  10. 10. Scrumban Board
  11. 11. Scrum vs Scrumban
  12. 12. Kanban ScrumbanRoles No prescribed role Team + needed rolesDaily scrummeetingNo meeting To make sure continuous work onrequirements and reduce idle timeof team members.SprintPlanningMeetingNo meeting. Can be done to plan to fill the slotsReview andRetrospectiveMeetingNot prescribed. Can be done as needed for processimprovement and share learnings.Work Flow Continuous Same as in Kanban. Just add limitof slots so that pull process willbecome more comfortable.Kanban vs Scrumban
  13. 13. Savita PahujaSavita.pahuja@gmail.comhttp://www.linkedin.com/in/savitapahuja13

×