this post was submitted on 09 Apr 2024
26 points (96.4% liked)
Programming
17390 readers
159 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
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
I don't understand how Agile became synonymous with "useless meetings." I thought the whole point of Agile was to minimize wasted work.
Management trying to look useful
My "scrum leader" (who we handled agile just fine without before) is constantly complaining about points or priorities shifting, to the point that he'll tell us to not put what we're actually working on on the board because it'll mess up the burndown chart.
One of the 4 values of agile is "responding to change over following a plan". He's parroted this to us before, and yet still doesn't seem to see the irony.
Agile was about reducing the power of micro-managers. They would have understood that if they could read.