Use of three simple measurements in to aid with improving software delivering. Includes real world data and a case study from three geographicaly distributed teams.
An updated version of Simple Measurements as delivered at the CT-SPIN group in 2012.
Many of things discussed has roots in Knowledge Management and ancient philosophy, beliefs and faiths. It is not new, but are generally ignored due to the strong influence of Taylorism especially in western contexts. This is an overview of things that work, that will need adoption in your context and are simple guidelines showing you how to do things.
Cynical answers are usually indicative of organisational pathology
You are not here to produce software, you are here to provide value to the business Also refer to Dave Nicolette ( http://davenicolette.wordpress.com/2012/08/14/how-to-avoid-the-local-optimization-problem-when-coaching-at-the-team-level-2/ ) “The goal is delivery effectiveness” Some still preach the Agile Manifesto, Some show you methods that will work
Credit to Bob Marshall for introducing me to the work of Billy Koen (Texas University)
From the work of Dorothy Leonard. Read “Wellsprings of Knowledge”
One always has to revisit classic batch development, as it is where most organisations are still stuck.
Read Don’s book: The Principles of Product Development. FLOW. Second Generation Lean Product Development Attention Principle: Time counts more than money
Use of an online system provides automated measurement. It is important not to negflect having a BIG VISIBLE BOARD
From “Quotable Kanban”
Eclesiastes 4:9-10 Two are better than one; because they have a good reward for their labour. For if they fall, the one will lift up his fellow: but woe to him that is alone when he falleth; for he hath not another to help him up.