Image via Wikipedia DevOps There’s quite a lot now on the internet about “devops” – combining development and operations work to increase flow and reduce problems
Google search for Kanban + Devops Links I’ve tagged “devops” One of the key features of this approach is the idea that above a certain threshold of estimated duration, all operations work has to be included in the kanban board for visibility and flow management.
Joe Dager (@business901) has posted a video interview with Dr. Michael Balle, the Gemba Coach at the Lean Enterprise Institute about Kaizen Teams without Kaizen Events, or Can Kaizen be part of Standard Work?
Balle makes some key points:
Standard work is about routine v non-routine, prescribed v non-prescribed
Standards are not the same as saying everything the same for everyone everywhere
Standards = a scientific process
Image via Wikipedia
I’m coaching a cross-functional team working across IT operations, application support and development, using Kanban to manage everything larger than the most immediate support requests.
They already appreciate the importance of reviewing their work and process, so we’ve been trying to make this into Standard Work.
Our first attempt is the 30 Minute Review and Retrospective
Review (max 10 minutes total)
Look at every story completed this week, for each (so ~1 min per story):