I do appreciate this line right here:
"However, not everything that isn't Waterfall is Agile, a fact that’s not always understood…"
However the article itself tackles a completely different subject.
On this matter though I'd suggest reading this article:http://grasshopperherder.com/lean-startup-in-the-enterprise-anti-pattern-the-lean-waterfall/
This is a decent article all-in-all as far as the tackling the subject of "cowboy coders" goes however I can't help from posting some of the truisms referenced in the article…
I'll try to keep all things fun and enjoyable though :)
"Agile is not Cowboy Coding, and Cowboy Coding is not unique to Agile teams" o_O
This took me a while to digest, however please allow me to rephrase that for people who paid attention during logic classes in high-school (in Romania we take logic classes during high-school, I believe it's the 9th grade):
"Apples are not salty and sweetness is not a unique trait of apples alone".
"Emergency situations that require quick, non-vetted changes to Production should be avoided at all costs." o_O
Yeah, while the rest of us, agile neophyte common programmers, are actually trying to achieve quite the opposite since forever.
"Working directly with Production code or with a source code repository that isn't versioned is a bad idea." o_O
This is not "cowboy coder"… this is plain out career path suicide. But then again you wouldn't get to have a career by doing this… So I don't know what this is exactly :)
"Without proper testing and documentation, you can’t prove your software works nor can anybody understand how it works." o_O
Never though about this before…
I usually just blame clients or call them mindless minions and send them references to readings of "Turing completeness" when I'm asked product related questions…
Since all software products are self-explanatory, self-contained and thus perfect and wonderful anyone who doesn't understand how they work or has any puzzling is basically a moron who shouldn't be entitled to own a computer…
"If you arm them with XP practices, Agile tools, a Kaizen mindset, and continued training and development, they can become model developers that contribute quality software time after time." o_O
Also, I think you might have missed a few ingredients: a pair of binoculars, one medium sized shoreline grey pebble, one silver bullet and a crystal ball…
Can't leave out the EPIC, mind blowing closure (AND also the reason for which I decided to write this):
"Just don’t make the mistake of trying to get them to do something for which there is no tangible benefit. They don’t take too kindly to that." o_O o_O o_O o_O o_O o_O o_O o_O o_O
Really? Who on Earth does take such a thing kindly?
So if you have someone in your team whom you get to do something for which there is no tangible benefit and they do take it kindly than they're either going to do a poor job, loose motivation or you've got Jesus in your team.