this post was submitted on 05 Jun 2024
413 points (94.4% liked)
Programming
16740 readers
258 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
Right off the bat i read
You need clearly defined requirements to write a good user story. Documentation comes after.
Precisely, once once have i worked in a company where agile was properly implemented and, yes, user stories were well documented and discussed before being developed. All others are just waterfall in disguise, or Fragile™.
This is the main reason the last company I worked for lacked in project delivery. They had just transitioned to Agile, and their whole teams lacked proper Agile experience and the training provided was very superficial. They barely put any time in refining the requirements and this trickled down to developers.
Projects that allow for clear requirements before really starting on them are clearly more likely to succeed than ones that have a higher complexity due to unknowns.