this post was submitted on 14 Dec 2023
20 points (85.7% liked)
Programming
17537 readers
129 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 [email protected]
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
In my experience it does not go without saying that a project needs a goal. Not a list of acceptance criteria or next steps, but WHY are we doing what's being asked. It's staggering how many times I've seen entire projects without a clearly defined goal or problem statement, and after 3 months the work was shelved. Management simply shrugged it off as, "That's business for you -- targets move," when plenty of people on the front line were unsure what the point was and it would've taken a 10 min convo with the intended audience to learn that the feature was nowhere in their top 10 and they'll never use it.