Search code examples
processagilemethodologykanban

How to stop Lean programming becoming Cowboy Coding?


My team has been progressively adopting more and more lightweight methodologies, moving from Scrum to Lean/Kanban where there is less and less formal process. At some point we will be back to Cowboy Coding; indeed I fear we may already be on the border line.

Where can the line be drawn between a very lightweight Lean and Agile process and anarchy? How will we know when we have crossed the line? And how can we prevent ourselves from crossing the line?

The question might also be phrased as, 'what processes cannot be safely eliminated in Lean's drive to eliminate waste'?


Solution

  • When something about the code is known or manageable by only one person in your group, you are under a big nice red-glowing "Saloon" sign, and you are basically pushing the doors.