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.
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.
Workflow of ScrumSprint Cycle
Workflow of kanbanNo “sprint end” – Continuous flow
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.
maintenance projects event driven workhelp-desk/supporthardening/packaging phasesprojects with frequent and unexpecteduser stories or programming errorsWhen to consider Scrumban
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 processesTo manage improvement communitiesduring/after Scrum roll-out
Scrumban Backlogavoid 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
Scrum vs Scrumban
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