this post was submitted on 25 Sep 2023
44 points (87.9% liked)
Programming
17416 readers
104 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 have my complaints about Agile, but a bit different from this list. Teams I've worked in have generally tried to spec in quality control measures into story points, to prevent some of the issues mentioned, for example.
My issue is almost always just that the top half of the organisation does not, and will never, conceptualise a software project like agile demands. Business will always want X scope within Y time. And Agile demands that at least one of those to be variable. The backlog represents scope organised by time. Want X features complete? Check the backlog to see when they'll be done. Want to deliver after Y time? Check the backlog to see what features will likely be ready by that time.
But business will not accept that. They have scope requirements and deadlines to deliver within.