Agile Is a Glass Cannon

Post by perelin » Sun, Mar 26, 2023, 7:11 AM UTC

boyakasha wrote: post #64

jayd16 wrote: post #13

Kinda misses the entire point of 'agile' which is a way to adjust to and gather changing requirements in an iterative process. It's a risk _mitigation_ strategy. I'm not sure I agree that anything is a glass cannon because it could work but you could also do it wrong so it could fail. If a team can't pull off agile what do they think would have been a safer strategy?

> It's a risk _mitigation_ strategy. It's designed to mitigate _delivery_ risk, not _organisational_ risk. > If a team can't pull off agile what do they think would have been a safer strategy? I would probably argue that Scrum (which I barely consider to be "agile") is more resilient to inexperience, and therefore lower risk. It's the McDonalds of processes. You're not going to get amazing results, but it will still…

Post by eesmith » Sun, Mar 26, 2023, 3:46 PM UTC

eurasiantiger wrote: post #83

eesmith wrote: post #75

Earlier quoted context omitted.

I've spent over 20 years thinking about it, and not been able to figure it out. Since it's clear to you, perhaps you can clarify how the Agile Manifesto applies to software product sales when there's a single developer and once-per-year product cycles?

Well, you do have a process there already — the release cycle. Why once per year?

Post by eesmith » Mon, Mar 27, 2023, 7:23 AM UTC

eurasiantiger wrote: post #85

eesmith wrote: post #84

Earlier quoted context omitted.

Sure, I have a process. I have 10K+ unit tests run across multiple OSes and Python versions, I have a checklist for release, and more. But if "a process" is all that's needed to be Agile then waterfall is Agile. Why not once a year? Does Agile require a higher delivery frequency than that? That is, how is your question relevant to the topic?

Individuals and interactions over processes, remember?