Marcus Hammarberg wrote:Kanban don't really say much about that but I think it's more of a generic question about how our work varies in size and complexity. For most software development projects I've come across there a large unknown factor in the outset of the project and we want to learn as much as possible about what we don't know yet (for more on that see this excellent video with Dan North: https://vimeo.com/43603453). The further we come along the project it more and more comes to just filling out the blanks.
I can see kanban support both those cases. Kanban is a tool for process improvements and helps us improve the flow of work (items) through any process. When we have a lot of exploring to do we might timebox the work items and say things like "This work item card represent us exploring requirement X for 5 days". After that we can decide if we need more exploration or if we have learned enough to feel that we have a grip on the risk involved with requirement X.
At the other end we can start to have a very predictable and stable process, so that we can say stuff like: "This is classified as a Small work item. They usually takes 2-3 days. Medium takes 3-8 and Large takes 5-20 days".
Marcus Hammarberg wrote:This is one of the reasons I often recommend against electronic boards, since they might constraint how we can evolve and change the board. They might not but just the risk of that have me shy away from them
Marcus Hammarberg wrote:It's a sickness in our community to look to tool. The tools are great but we don't want to be slaves under them.