I've been employed as a developer since 1988. We had private office, minimal interruptions, one meeting per week. We enjoyed our work, we got a lot more done, we had fewer bugs.

I see no value in the methodologies at all. As you note, no two people have the same understanding but there is one effect that is above dispute: the methodologies add more meetings, more interruptions, more extra work, more process./

I've argued this in many articles here and don't want to repeat them in a response, but I do have one thing to say.

"Stories" as a neologism for "user scenarios" is offensive and degrading. It sounds like kindergarten. Where are the milk and cookies? It's like Safeway cashiers forced to wear pilgrim hats at Thanksgiving.

Agile brings in a whole steaming pile of new words for non-new ideas. And most of them lack precise definitions; ten people saying "refactor" will mean ten different things. "Technical debt" is just unfinished work but sounds more intelligent.

I either work solo, or I work in groups with very high divisions between responsibilities, or I do technical writing. I will never work onsite again. Not with daily scrums, annoying nomenclature, "teams," or any of that. It's over.

American Software Developer living in Vietnam. Classical musician (guitar, woodwinds), weightlifter, multilingual, misanthrope • XY

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store