Menu
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'?
953
Cowboy coding is an undisciplined approach to software development that gives programmers complete control over the development process. In this context, cowboy is a synonym for maverick -- a loner who does things his own way.
Cowboy coding is software development where programmers have autonomy over the development process. This includes control of the project's schedule, languages, algorithms, tools, frameworks and coding style.
WHAT IS COWBOY CODING? Cowboy coding is a style of software development that gives individual programmers complete control of all aspects of the development process. Unlike traditional software-development methodologies such as waterfall development, cowboy coding does not follow a defined approach.
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.
54
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
