4 ms·

Yeah, scrum is the “nobody got fired for buying an IBM” of 21st century project management systems.

Zigurd 5y ago
A good starting point for Scrum skepticism is that none of the Scrum jargon terms are in the Manifesto for Agile Software Development.
- eesmith 5y ago
  I don't think that's a valid inference. Quoting Wikipedia at https://en.wikipedia.org/wiki/Scrum_(software_development) https://en.wikipedia.org/wiki/Scrum_(software_development) : > In the early 1990s, Ken Schwaber used what would become scrum at his company, Advanced Development Methods; while Jeff Sutherland, John Scumniotales and Jeff McKenna developed a similar approach at Easel Corporation, referring to it using the single word Scrum.[16] > Sutherland and Schwaber worked together to integrate their ideas into a single framework, scrum. They tested scrum and continually improved it, leading to their 1995 paper,[17] contributions to the Manifesto for Agile Software Development in 2001,[18] and the worldwide spread and use of scrum since 2002. (I verified that with a Google Book snippet for that 1995 publication, which says: "More recently, a refined approach to the SCRUM process has been applied by Sutherland to Smalltalk development and Schwaber to Delphi development. The SCRUM approach is used at leading edge software companies with significant success.) You can see both Sutherland and Schwaber are signatories to the Manifesto. I think it's unlikely they would be signatories if the Manifesto was not aligned with principles of scrum.
  - Zigurd 5y ago
    The Scrum way of doing Agile is mostly fine, especially as the people who created Scrum define it. The problems with Scrum that I have seen are mostly the result of expedient training. Scrum is a victim of its own success in that way. Scrum jargon combined with a recipe-based application of Scrum makes things worse. Some Scrum jargon is counterproductive on the face of it. "Sprints" imply working faster. "Product owner" is often a debased form of product management. There is a normal English word for everything in Scrum.

A good starting point for Scrum skepticism is that none of the Scrum jargon terms are in the Manifesto for Agile Software Development.

eesmith 5y ago
I don't think that's a valid inference. Quoting Wikipedia at https://en.wikipedia.org/wiki/Scrum_(software_development) https://en.wikipedia.org/wiki/Scrum_(software_development) : > In the early 1990s, Ken Schwaber used what would become scrum at his company, Advanced Development Methods; while Jeff Sutherland, John Scumniotales and Jeff McKenna developed a similar approach at Easel Corporation, referring to it using the single word Scrum.[16] > Sutherland and Schwaber worked together to integrate their ideas into a single framework, scrum. They tested scrum and continually improved it, leading to their 1995 paper,[17] contributions to the Manifesto for Agile Software Development in 2001,[18] and the worldwide spread and use of scrum since 2002. (I verified that with a Google Book snippet for that 1995 publication, which says: "More recently, a refined approach to the SCRUM process has been applied by Sutherland to Smalltalk development and Schwaber to Delphi development. The SCRUM approach is used at leading edge software companies with significant success.) You can see both Sutherland and Schwaber are signatories to the Manifesto. I think it's unlikely they would be signatories if the Manifesto was not aligned with principles of scrum.
- Zigurd 5y ago
  The Scrum way of doing Agile is mostly fine, especially as the people who created Scrum define it. The problems with Scrum that I have seen are mostly the result of expedient training. Scrum is a victim of its own success in that way. Scrum jargon combined with a recipe-based application of Scrum makes things worse. Some Scrum jargon is counterproductive on the face of it. "Sprints" imply working faster. "Product owner" is often a debased form of product management. There is a normal English word for everything in Scrum.