4 ms·

Perhaps I'm not an expert, but I always felt there are things left out by the more popular methodologies. This article scrapes the surface: https://michaeloch

by majke 8y ago

Perhaps I'm not an expert, but I always felt there are things left out by the more popular methodologies. This article scrapes the surface: https://michaelochurch.wordpress.com/2015/06/06/why-agile-and-especially-scrum-are-terrible/ https://michaelochurch.wordpress.com/2015/06/06/why-agile-an... > "The worst thing about estimates is that they push a company in the direction of doing work that’s estimable. This causes programmers to favor the low-yield, easy stuff that the business doesn’t actually need but that is 'safe'". > "Good engineers want to work in engineer-driven firms where they will be calling shots regarding what gets worked on, without having to justify themselves to 'scrum masters' and 'product owners' and layers of non-technical management" > "Scrum [is] tailored toward the body shops where client relationships are so mismanaged" > "Open-plan offices are the most egregious example. They aren’t productive" > "[Scrum is] Like a failed communist state that equalizes by spreading poverty" There is more. In "pure scrum" it's not obvious how to account for refactoring, developer experimentation, improving infrastructure (or creating one from scratch!), making tests better. Product driven things - sure, can be driven by scrum. But what to do when work is driven by engineering?

gaius 8y ago
Right, Agile is for outsourced/offshore teams cranking out intranets or shopping carts or adding another minor feature to an existing codebase written by someone else. Like maintenance on a legacy app. The kind of work that good engineers thrive on - a hard problem starting with en empty Emacs buffer - is something that the methodology merchants have never experienced themselves. The only product they ever shipped is the methodology itself! I say this as a one-time “certified scrum master”.
- prepend 8y ago
  This is a pretty tough statement to defend. Take a look at the myriad of open source projects, or just limit it to Apache’s http://apache.org/index.html#projects-list http://apache.org/index.html#projects-list and you’ll see a bunch of “empty emacs buffer” projects with a long audit trail of agile development. Not necessarily scrum.
  - gaius 8y ago
    My only personal experience of agile is scrum, so I will concede your point :-)

by majke 8y ago

gaius 8y ago

Right, Agile is for outsourced/offshore teams cranking out intranets or shopping carts or adding another minor feature to an existing codebase written by someone else. Like maintenance on a legacy app. The kind of work that good engineers thrive on - a hard problem starting with en empty Emacs buffer - is something that the methodology merchants have never experienced themselves. The only product they ever shipped is the methodology itself! I say this as a one-time “certified scrum master”.

prepend 8y ago
This is a pretty tough statement to defend. Take a look at the myriad of open source projects, or just limit it to Apache’s http://apache.org/index.html#projects-list http://apache.org/index.html#projects-list and you’ll see a bunch of “empty emacs buffer” projects with a long audit trail of agile development. Not necessarily scrum.
- gaius 8y ago
  My only personal experience of agile is scrum, so I will concede your point :-)