4 ms·
As usual no one can agree what agile actually is. Is what you are doing agile? Some would say no. Some would say yes. Someone will likely says agile is a lot o
by collyw 7y ago
As usual no one can agree what agile actually is. Is what you are doing agile? Some would say no. Some would say yes.
Someone will likely says agile is a lot of shit and someone will reply saying "you are doing it wrong" without giving any indication of how to do it right.
- jdmoreira 7y agoagain here is my opinion... The minimum requirement for doing agile IMHO is to have retros and to iterate the process all the time until it works. That’s it. But what agile is or is not is just semantics. It’s irrelevant I think. Who cares if we all follow the same set of rules? People selling certifications that's who!
- AnimalMuppet 7y ago> and to iterate the process all the time until it works. YES! If you aren't able to hack the process, then you aren't agile. Any rule-book driven "agile" isn't agile. The problem is, to do agile, you need managers that don't have to have a rule book to follow. Those are rare. If you don't have them, then you get somebody's rigid "agile process", but not much actual agility.
- wan23 7y agoSame! Whenever I have to explain what agile is I start with retrospectives. It's the one rule that is mandatory. Standups, sprints, JIRA boards, grooming/refinement sessions and everything else in a heavyweight framework like scrum is there to support the principles of agile, but none of it is actually necessary. IMO every software developer should read the Agile Manifesto ( https://agilemanifesto.org/principles.html https://agilemanifesto.org/principles.html ) every once in a while and consider whether their process is actually working for the team.
- JohnFen 7y agoIf that's the case, then I've been doing agile for decades before agile was a thing! So I guess waterfall is agile...
- jvagner 7y agoAgreements with gates. Usually short term.. iterate and improve.
- saidajigumi 7y agoThis is because the naive mental model of development processes is bullshit: the techniques introduced and used should never be some rigid dogma. This applies to "agile" or whatever flavor-of-the-year we're talking about. Agile is best thought of as an ecosystem of tools used to shape software (and knowledge) work. Am I "doing it wrong" when I get out my toolbox, use the #2 Philips head screwdriver, but not the torque wrench? NO! Not if I didn't need the torque wrench! And that's a massive source of pain with "agile", or what I think of as "kitchen sink agile" where the goal becomes, explicit or not, to apply as many processes from as many books as possible – instead of picking just the right ones. I've literally never been on two teams with the same process needs in my entire (now long) career. Even those teams year-over-year evolve their needs as the members, organization, and business change. Why should the process therefore be a static entity? One of the very few fixed rules I've learned hits to the GP's theme: it's critical to have the least necessary process, just as it's ridiculous to break out every tool in the box just to tighten up a loose screw.
- fuzz4lyfe 7y agoMuch like communism, agile is only agile while it is working well.