4 ms·
Correct, it's not "pure" agile, because that version of agile is extremely frustrating to implement inside any organization that's not a consultancy. That shoul
by spamizbad 4y ago
Correct, it's not "pure" agile, because that version of agile is extremely frustrating to implement inside any organization that's not a consultancy. That shouldn't surprise you: capital "A" Agile grew out of consultancies. It's not a good fit for product-driven technology firms, but product-driven firms try to adopt small "a" agile principles.
The temptation to say "If you're not enjoying yourself you're doing it wrong" doesn't really work here. Agile was not shaped by technology firms or a product culture. Its roots are in a contract job to rewrite a payroll system at a Fortune 500 company and if that's your line of work then you can hew closer to “pure” agile. The rest of us are handed a process we have to make work inside an existing org.
- koonsolo 4y agoI haven't worked in any 100% pure agile team either. But the main point I was trying to get across is that the parts that work against proper development is not where you follow the agile part, it's where the agile part isn't followed.