Scrum, Scrum-ban, Kanban
I've been hearing about Kanban methodology for weeks. Finally, I had a chance to read quite good comparison Scrum and Kanban thanks to Henrik Kniberg. The basic rules of Kanban are presented below.
My thoughts on Kanban
WIP. Defining the work in progress per given state (column at whiteboard) seems as nice idea. Thanks for this you can set a state’s capacity and you can ensure that the team would not be disrupted by asking for some urgent thing to do and you keep your team busy. The interesting thing is how to set this right "capacity". Hmmm.. Kanban says the team needs to give a few tries to find out correct number – there is no example how to designate it.
Commitment. According to Kanban there is no defined time period for delivering given functionalities. My concerns here are doing a demo builds and delivering releases. How should we do them? Should we wait for customer’s request? Should we add then new request into "TODO" column? Would event-driven approach work? Is the lack of commitment the right thing? Kanban does not mention release plan at all (prioritized product backlog in SCRUM), so the common goal is not visible to the team. Would it demotivate people? What are the priorities for "TODO" column? Should team take the most top one?
Finally. How Kanban can work in fixed-price project?
What about merging Scrum and Kanban making Scrum-ban? What’s your feeling? Do you think it could work?
My thoughts on Kanban
WIP. Defining the work in progress per given state (column at whiteboard) seems as nice idea. Thanks for this you can set a state’s capacity and you can ensure that the team would not be disrupted by asking for some urgent thing to do and you keep your team busy. The interesting thing is how to set this right "capacity". Hmmm.. Kanban says the team needs to give a few tries to find out correct number – there is no example how to designate it.
Commitment. According to Kanban there is no defined time period for delivering given functionalities. My concerns here are doing a demo builds and delivering releases. How should we do them? Should we wait for customer’s request? Should we add then new request into "TODO" column? Would event-driven approach work? Is the lack of commitment the right thing? Kanban does not mention release plan at all (prioritized product backlog in SCRUM), so the common goal is not visible to the team. Would it demotivate people? What are the priorities for "TODO" column? Should team take the most top one?
Finally. How Kanban can work in fixed-price project?
What about merging Scrum and Kanban making Scrum-ban? What’s your feeling? Do you think it could work?
Etykiety:
kanban
The aim of implementing Kanban system is to limit the team’s Work In Progress based on the agreed capacity and to increase overall throughput. Identifying issues that impair performance helps maintain a steady flow of work, thereby having an overall impact on quality. This shortens lead times, which, in turn, improves the system’s predictability.
One of the criteria for selecting an agile tool in terms of Kanban or Scrum can be the time required. One of these methodology works well when there is shortage of time in terms of deadlines; the other one works well in situations where more time is required to carry out tasks when a diminutive iteration cannot satisfy the work.