First step of agile transformation is to decide which methodology to use. The most popular agile methodologies are Scrum and Kanban. While Scrum is revolutionary, Kanban provides an evolutionary transformation. Both methodologies have different practices and techniques that maximize productivity. While Scrum is preferred in software development projects, Kanban is mostly used in teams which doing operational and support tasks.

There are some teams, doing both software development and operational/support works. I have observed on these teams some of the scrum practices are insufficient. For example, The teams are planned %80 of capacity at sprint planning meeting and the other %20 is used as buffer for unplanned works. But %20 buffer is unsufficient for this type of teams. Or there can be frequent changes in PBIs that have been committed at sprint planning meeting. To give up Scrum is to get away from Scrum’s discipline and prevent the software development teams from becoming agile. These teams don’t do only operational/support works, also kanban doesn’t meet the need.

While talking about Scrum or Kanban, Scrumban was emerged as a hybrid of these two methodologies. Before implementing Scrumban, the practices/techniques in the scrum and kanban which are useful for the team, should be determined. The point to note here is that to determine which core method and features are taken. The methodology which determined as the core should be added the practices/techniques in the other methodology.

Since it is the main business software development, and to benefit from the discipline in Scrum, it is more efficient to add on Scrum with Kanban practices.Sprint planning, retrospective, review and daily scrum rituals which are in scrum features provide continuous improvement and is managed sprint process. Making these rituals are optional can damage the agile transformation since cause to move away from Scrum’s discipline.
Because Kanban is also a technique that increases the productivity that can be applied to waterfall.Experiences say that waterfall and agile don’t walk together in a project.

Well, Which Kanban techniques are increased efficiency when practicing Scrum?

Work In Progress Limit: I have observed and even experienced that some teams which practicing Scrum have accumalation in the test stage tasks especially towards the end of sprint . In these situations doing out of test tasks will only increase test tasks and this approach also serves to increase NOT DONE tasks.According to teams expertise, determining In Progress limit will increase the number of DONE PBI’s.

Measure Cycle/Lead Time: In some teams, the tasks that come from the business units are divided into many parts for only can say “be comfortable, we started”, and it takes a long time to completed. It has been interesting to me except unusual cases, a prioritised task in a sprint doesn’t take priority the next sprint. It will increase awareness of when a PBI comes and when it is delivered to the business unit.

Change in board status: In the software development process, seeing the status of BPI’s on stage by stage basis will increase efficiency and will increase awareness by put system on PBI’s.

Finally I can say that, in software development process it would be more efficient to determine Scrum as a core method and add Kanban practices on Scrum features

Leave a Reply

Your email address will not be published. Required fields are marked *

Check Also

Scrum’da proje yöneticisi var mı?

Scrum’da scrum master, product owner ve development team dışında bir rol yok gözüküy…