A Kanban System for Software Development
Prior to September 2007, my team was using traditional Scrum; a t-shirt sized and prioritised Product Backlog, two week Sprints begun with a two hour planning meeting and ended with a two hour review and retrospective meeting, and Sprint Burndown and Velocity as the primary metrics. However, despite the team completing Product Backlog Items every sprint, and making regular releases, …