We are currently using Kanban to manage customizations and extensions within our application.
Our application is an enterprise application which is highly configurable, however, configure the tool right is quite complicate. The development of our tool have been taken place during several years (about 15), and the code is quite complex. Furthermore, the requirements and specifications from the customers are highly volatiles. They often change substantially before the end of the project. Therefore, we need a flexible (agile) process to adequate these changes into the project.
Our current Kanban board counts with the following status/columns: * Specifying * Specify-Approving * Rejected * Ready for dev/conf * on progress (dev/conf) * Testing * UAT * Done.
In my perspective, our current problem with our implementation of Kanban is that we are not including essential information which should be required stage after stage before being moved from one to other column. E.g Software Specification, Acceptance Criteria, Testing Plan, Release Notes... I see that including these items might increase the complexity of the Kanban process, and this makes me question if Kanban is the right solution that we need.
On the other hand, I feel that our Kanban implementation is not giving use the flexibility that we want. The requirements often change before completion of the project.
- Is kanban the right solution for project similar to ours?
- How can I modify our Kanban process to be more efficient?
- What alternatives are for Kanban for this kind of projects?