hamstar
commented
12 years ago I reckon we use Kanban because it is a very malleable methodology and will enable us to work in the way that best suits us.
- Iterations: we can use iterations, queueing up features to be completed and then doing a release at the end of the iteration.
- Visualizing work: using a kanban board it is very visual and you can see at a glance what stages the work is in
- Problem visibility: The flow will stop if there is a problem. This makes problems visible quickly, allowing them to be corrected ASAP.
As outlined in our plan, we had planned to use ScRUPban, which is a combination of the Scrum and Kanban process.
"Elements from Rational Unified Process, Scrum and Kanban to create a very adaptive methodology but still with a clear overall goal"
James, however suggests that we use 1 methodology and not create our own.