3 ms·
again 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. B
by jdmoreira 7y ago
again 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.