102
I hate agile
(hexbear.net)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 28 Oct 2024
102 points (98.1% liked)
technology
23313 readers
127 users here now
On the road to fully automated luxury gay space communism.
Spreading Linux propaganda since 2020
- Ways to run Microsoft/Adobe and more on Linux
- The Ultimate FOSS Guide For Android
- Great libre software on Windows
- Hey you, the lib still using Chrome. Read this post!
Rules:
- 1. Obviously abide by the sitewide code of conduct. Bigotry will be met with an immediate ban
- 2. This community is about technology. Offtopic is permitted as long as it is kept in the comment sections
- 3. Although this is not /c/libre, FOSS related posting is tolerated, and even welcome in the case of effort posts
- 4. We believe technology should be liberating. As such, avoid promoting proprietary and/or bourgeois technology
- 5. Explanatory posts to correct the potential mistakes a comrade made in a post of their own are allowed, as long as they remain respectful
- 6. No crypto (Bitcoin, NFT, etc.) speculation, unless it is purely informative and not too cringe
- 7. Absolutely no tech bro shit. If you have a good opinion of Silicon Valley billionaires please manifest yourself so we can ban you.
founded 4 years ago
MODERATORS
There's an old saying that a pig doesn't get any fatter by being weighed and there's a lot of pig-weighing going in the software industry.
To me personally scrum rituals like daily standups are a minor nuisance. They are unproductive and often boring but most of the time you can get them over with relatively quickly.
What I really, really, really hate is the time registration tyranny where you have to do estimates, have meetings about estimates, remember to turn on and off timers, fiddle with timesheets when you forget about the timers, answer questions like "how will this change that everyone agrees needs to be done affect the estimates?" and defend why a task that was estimated to six hours took eight to complete.
I have ADHD, I have trouble making a realistic estimate on how long it takes to cook pasta and you expect me to be able to accurately predict how long it takes to compete a 3000+ hour project with a ton of external dependencies, arcane legacy code and agile constantly evolving requirements?
I understand that you need something to put on a bill that the customer will pay without complaining but come on, how can this be effective? Sometimes I feel I spend more time wrangling timesheets than actually coding.
There’s a 2:3 ratio of time-estimators to doers at my current company and the devs have to spend about 20-25% of their time estimating their time.
I had enough pull to make a “hit squad” unit that “just executed” and everyone was stunned at how we managed to pull off a from scratch release in “just” 8 months, honestly compared to previous companies that was slow but I also had to train up 5 junior/mids who had never worked with Go or Kubernetes at the same time, saving the company potentially millions in expenses and making a product they are already selling to clients.
Now they’ve assigned a product owner and have asked us to start doing daily’s so I’m going to quit.
SCRUM is middle-management capture and all the middle-managers know they are not necessary.
Exactly. Management in the since of coordinating teams/organizations is not a fake job in and of itself, but the amount of bloat/inflation that has occurred to management has made a solid 90% of the "job" a make-work job.
Same. The time tracking is one of those things the more you spend time doing the more you realize it's a waste of time.
That's one big reason I hate how individualized software development. It's crazy that it's all YOUR job to handle all that. There is no team, no collective, just single nodes in a collection of nodes. It's really a shame.
I get your point about how individualised development is part of the problem. I just want to point out how these rituals to divine the future of a project can become absolutely cursed when done as a team effort. Sitting by yourself and pondering how long it will take to make the computer go beep is a miserable experience, having to discuss the minutiae of how long something will take because management got the idea that this will make the estimates "more accurate" is many times worse.
BIG AGREE on that one