I’ve recently settled on a visual representation of Kanban Thinking which has been working well. The structure took shape when I realised that Flow, Value and Capability were system impacts. Those are the arrows coming out of the right hand side of the central System. The arrows going into the left hand side are the levers we have to influence the system behaviour; Study, Share, Limit, Sense and Learn. The primary lever is limiting. Studying and sharing provide the transparency and visibility to enable the limits. Sensing and learning give the feedback to evolve the limits.
Feel free to use this picture. I hope it proves useful.
David Harvey posted a brilliant piece on his blog entitled “The Scrum Picture is Wrong”. I highly recommend reading it. His ideas and suggestions for an alternative Scrum picture got me thinking about how to visualise Lean and Agile software development in a process or label agnostic way. David’s picture looked like a figure of eight, and there seemed to be 2 inputs (a vision and reality), and 2 outputs (the product and the team). A quick google found me what I was looking for here – a figure of eight with a bar across the top and bottom. “A time sign that according to Diderot’s Encyclopedia meant hour for the chemists in eighteenth century France”. That seems quite appropriate. An hour would be quite a good interval for a feedback loop 🙂
This is what I came up with. A vision and reality come together to produce a product and a team through process and improvement (and process improvement)
Now I just need to find a good label to stick on it…