Scrum vs Kanban
The Kanban vs Scrum debate is a completely pointless argument. Each solves a set of problems. The problems they solve are complementary.
The Kanban vs Scrum debate is a completely pointless argument. Each solves a set of problems. The problems they solve are complementary. There may be times when aspects of Scrum may not be applicable, such as working with IT Operations teams but generally they’re complimentary with each other. At Solutioneers we find many of our clients start out with Scrum practices but overtime they soften the sprint boundaries and move to a continuous flow model of delivery. Once you make the transition from Scrum to Kanban you may retain some of the practices of Scrum. Examples include Sprint planning. Sprint planning in Kanban is useful when organising the demand or backlog. Although the team may not be utilising Sprints for delivery, planning ahead in terms of two week deliveries can be useful for some stakeholders. So if you hear people arguing over Scrum vs Kanban, just point them at this argument.
Related articles
Beyond Cycle Time: Introducing Flow Style and Mileage for Agile Teams
Flow Style and Mileage. Understand team dynamics, pinpoint inefficiencies, and elevate your Agile processes for superior performance.
Agile user stories vs sub-tasks
The Flaws of Using Sub-Tasks to Organize Work in Agile Software Development and Why Moving Stories is the Key to Success
50 example user stories for Agile Software Development
A collection of real user story examples for you to copy & paste. Useful for teams new to Agile ways of working.