Agile Is Dead
agilepilled.com
Agile Is Dead
1–10 of 99 posts
Re: Agile Is Dead
#2[deleted]
Re: Agile Is Dead
#3From the enterprise perspective, the purpose of Agile was to fail while giving the appearance of the greatest and most conscientious possible effort. "If it can't be done this way, it can't be done at all": time to gift more tens of millions of dollars to IBM and Oracle and Microsoft.
Re: Agile Is Dead
#4[flagged]
Re: Agile Is Dead
#5it was never alive to begin with. certainly not in the real world.
Re: Agile Is Dead
#6From the enterprise perspective, the purpose of Agile was to fail while giving the appearance of the greatest and most conscientious possible effort. "If it can't be done this way, it can't be done at all": time to gift more tens of millions of dollars to IBM and Oracle and Microsoft.
Not all that counts can be counted.
Not all that can be counted counts.
I hate Agile and I'm not going to try and sugar coat that. "We're drowning under the weight of clueless product leads, managers, and owners who've never written a line of code" That's why this still exists though not performant, because it some peoples entire entire careers now.
Re: Agile Is Dead
#7From the enterprise perspective, the purpose of Agile was to fail while giving the appearance of the greatest and most conscientious possible effort. "If it can't be done this way, it can't be done at all": time to gift more tens of millions of dollars to IBM and Oracle and Microsoft.
Agile is dead long live (fr)agile.
Re: Agile Is Dead
#8the purpose of agile was to align the most requested feature work to the most expensive pay cycles. the purpose of devops was to get two for the price of one. everything else has been content marketing or people parroting whatever they thought would get them a raise.
Re: Agile Is Dead
#9When I hear about Agile these days, it's almost always an excuse not to do the right thing. The last time it came up was someone resisting defining our company's product delivery process, which has always suffered from a lack of clarity. The time before that, it was someone saying "Let's be Agile about this", but meaning "let's do a shitty version of this, and pretend we'll come back to it later, rather than just moving on to the shitty version of the next feature."
The response that "you're not practicing Real Agile" may be true, but is unhelpful, as this is the norm rather than the exception. A consistent failure of any plan to succeed in its purpose after 25 years is a failure of that plan, not of the world, at least when the plan promises improvement on a shorter-than-generational timeline.
The only time I've ever seen Agile work is when the technical lead who practiced it was incredibly charismatic and forceful, and the team wanted to do what he said. Like magic. It worked great, and then the guy left, and the whole thing fell apart within months. But, I don't think what worked about that team was Agile per se, I think it was a unique individual leader that made it work, and it would have been just as successful without Agile.
I'm skeptical about methodologies. The force of the team and the company they're embedded in is so strong, it will overcome a generic system in most cases. I think you probably have to make an ad hoc solution that continually evolves, and have someone with rare abilities prune it and champion it. That is so harder. In all likelihood, muddling along is probably the realistic solution for most companies.
Re: Agile Is Dead
#10> It's for those who believe that skilled engineers are the true drivers of innovation and creators of meaningful products.
Maybe the only thing I feel iffy about here. Just feels a bit naïve, I've worked together with some really talented designers. Also worked with some really talented product owners. Can't say I've agreed with every marketer/PR person I've worked with but they've saved our ass a few times. While I do think developers have a major role to play, I don't think a company past a certain size would benefit from only devs making all decisions. A little specialization is OK when there is actually a useful task at hand.
There's innovation to be made on design or business side stuff as well. Maybe sort of lame to you, but it's helped me make stuff in the past.
Nothing to do with Agile btw, hopefully this doesn't sound like I'm pitching the tech world's private definition of capital A "Agile" with a different lens. Just a plea to appreciate that engineers aren't multitasking super gods.