this post was submitted on 06 Jun 2024
477 points (89.3% liked)
Technology
59349 readers
5340 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Yeah, Agile isn't really at fault here. If done right - if you've got a scrum master, a proper product owner, proper planning and backlog grooming, etc. - it works really well. The problem is some companies think Agile is just "give the devs some pie-in-the-sky hopes and dreams, let 'em loose, and if they don't give half a dozen execs exactly what they want (despite their massively conflicting ideas on what they want), cancel the project."
In one the worst “poor planning” projects I’ve been in the product owner just kept sneaking in new “high priority” issues to the top of the backlog throughout the sprint. I don’t think we had a single sprint where we ended up with fewer open issues in the backlog than when we started.
Needless to say, he was the main reason why I quit.
In my experience it's just kanban, but make the devs feels guilty between sprints for not meeting their goals.
Absolutely It's so management can say "your velocity was down 15% this sprint" and not feel bad about it instead of saying "work more" It's plausible deniability for demanding unpaid overtime
This is what ticks me off about the "Agile" brand, it's chock full of no true Scotsman fallacy (if a team failed while doing "Agile", it means they weren't being "Agile").
I can appreciate sympathizing with some tenets as Agile might be presented, but the popularity and consultancy around it has pretty much ruined Agile as a brand.
Broadly speaking, any attempt to capture nuance of "best practices" into a brand word/phrase will be ruined the second it becomes "popular".
This isn't a case of No True Scotsman. There really is a right way and a whole lot of wrong ways to do Agile development. Any team that calls itself an Agile team that doesn't actually follow the processes properly is doing it wrong and will fail.
That doesn't mean any team that's doing it right will succeed, but it's like riding a horse: If you only climb halfway up the horse and try to hold on while at a 90-degree angle, it's not going to work, and it would be stupid to declare that the concept of horse-riding is broken. No, it's not broken, you're just an idiot who thought you could ride a horse while only halfway up, clinging desperately to its side.
I mean, this statement is also weird, to imply that not following Agile implies failure. I'd say it's quite possible for a team to "falsely" execute on Agile and still pull off success. However, if that story is prominent and successful, no one is going to make a peep about it not being "true Agile", they'll only do that when it's a failure.
But really this detail is beside the point, that people want to use 'Agile' as shorthand for good methodology, but it's the way of the world that any shorthand that is popular will get co-opted and corrupted to the point of uselessness. You end up with various "interpretations" and so the meaning is diluted.
Now at a glance, this may seem an innocuous scenario, ok, Agile doesn't "mean" anything specific in practice because of people abusing it to their objectives, but it still carries the weight of "authority". So if you have a criticism like "there's way too many stupid pointless required fields in our Jira implementation, and there's a super convoluted workflow involving too many stakeholders to walk a simple ticket to completion", then you get chastised because "our workflow is anchored in Agile, and you can easily see online that Agile makes success, so you obviously don't understand success". You can try to declare "Individuals and interactions over processes and tools", but then they'll say "oh, but the stuff on the right is valuable, and it's used to facilitate the interactions between people". Thanks to Atlassian marketing, for a lot of the corporate world if you implement it in Jira, then it is, by definition, "Agile" and your peons can shut up because you are right.
Basically, things get ruined by trying to abbreviate. You may be able to cite the Agile manifesto as something specific enough yet still short, though it's still wishy washy enough to not be able to really "win" an argument with someone when deciding how you are going to move forward.