4 ms·
> Suffice it to say, it's all been accounted for. Agile works. And if you are doing "Agile" but it's not working... then you're Doing It Wrong(tm). Right?
by jacobyoder 5y ago
> Suffice it to say, it's all been accounted for. Agile works.
And if you are doing "Agile" but it's not working... then you're Doing It Wrong(tm). Right?
- TameAntelope 5y agoWould it make you feel better to hear it's not your fault? There are lots of reasons agile won't work for you, but they're also great indications you should probably leave a given org.
- jacobyoder 5y agoWhy not just say "Agile Works Sometimes"? Or "Agile Can Work"? Because when "Agile Works" is touted, and then things go wrong, people get blamed, vs the actual processes and concepts. If "Agile Works", but we're not getting the results, then someone must be doing something wrong - can't be "Agile" that's wrong (for this scenario). "Agile" software development doesn't work when there's 5 non-technical stakeholders and 1 software developer.