Scrum and Kaban are two Agile approaches that could be used in software development, depending also on the context of the software development tools. In his blog post “Ditching Scrum for Kanban — The best decision we’ve made as a team”, Grant Ammons shares some thought on why he successfully changed it process from a Scrum to a Kanban perspective.
At the beginning of his book, Allan Kelly describes Xanpan as both a method and a philosophy, his philosophy on how software is, or should be, created, and how Agile works, or should work. If Xanpan is basically a mix of XP (eXtreme programming) and Kanban, it contains ideas and techniques of other Agile and Lean approaches, focusing on how teams should work together to deliver better software and value.
In the context of software development, Kanban is an approach based on Lean that tries to limit waste and work in progress to the actual capacity of the software development team. The aim of Kanban is to create a context that balances capacity and demand through a value stream. Thus the work is not “pushed” to developers by project managers, but “pulled” by the development team according to priorities. Kanban is the Japanese word for visual card and visualizing the current situation is very important in Kanban. If collocated teams can use simple dashboards and cards to track the work in progress, this is not the same for large or distributed Kanban teams that need to use tools.
Redmine is a popular open source project management web application. It was written using the Ruby on Rails framework. This software is more oriented towards a traditional approach for project management with Gantt charts and calendar than Agile, Scrum or Kanban. However, Redmine architecture allows however creating plugins to add additional features. The development of a number of Agile and Lean plugins has therefore been started in these past years. However not all those plugins have been in continuous development until the current release of Redmine 3.3
Bugzilla is a popular open source bug tracker created originally by the Mozilla Foundation. It has an open architecture that allows extending its basic functionalities. This article lists the Bugzilla plugins, called add-on in Bugzilla, that allows integrating an Agile project management approach like Scrum or Kanban around the bug tracking features of Bugzilla.
This talk is a study of a case in which three Scrum teams converged into a single large team Kanban system design. Working in separate teams resulted in issues with responsibility, hand-overs, resource utilization and a culture of blaming others. In a large, highly self-organized team the members could share responsibility for the whole, work on the right things and focus on flow.
Scrum, Kanban, Scrumban: there are many approaches to manage product development and project in the Agile software development world. It is a good thing to have multiple Agile tools, but you should also know when to use them. In this article Brendan Marsh of Spotify explains why his team dropped Scrum for Kanban just before launching their product.