3 ms·

> there is no governing body to determine whether you are agile or not Tell that to agile advocates who are always quick to point out that when a project using

> there is no governing body to determine whether you are agile or not Tell that to agile advocates who are always quick to point out that when a project using Agile fails, it's never Agile's fault, it's always because the team didn't apply Agile correctly. It's the text book definition of "No True Scotsman".

exelius 11y ago
Those "agile advocates" are just trying to sell their own services to improve your "agile functioning". Shame on you for falling for it. Agile is so widespread at this point that "doing Agile wrong" isn't a reason teams fail. Most Agile teams fail for reasons outside the development process. Ineffective leadership, lack of experience, poor product focus, etc. These teams would have failed with a waterfall model too; it would have just taken longer to realize it.
- noarchy 11y ago
  >Those "agile advocates" are just trying to sell their own services to improve your "agile functioning". Shame on you for falling for it. Agile is so widespread at this point that "doing Agile wrong" isn't a reason teams fail. To be fair, it isn't often the individual developer who "falls" for it. These management methodologies are imposed on them, and the developer has to learn to roll with it. You may not be in a position to determine whether or not a project manager was sent off for "Scrum master certification".