this post was submitted on 06 Jun 2024
477 points (89.3% liked)
Technology
59349 readers
5260 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
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 feel like that's the same underlying issue: The requirements are not understood upfront.
If a customer cannot give you any specific information, you cannot cut any corners. You're pretty much forced to build a general framework, so that as the requirements become clearer, you're still equipped to handle them.
I guess, the alternative is building a prototype, which you're allowed to throw away afterwards. I've never been able to do that, because our management does not understand that concept.
Actually on most of these failed projects the requirements of the original customer were pretty clear. But the developers tried to go far beyond those original requirements. It is fair to say that the future requirements were not well understood.
Lol I've done many prototypes. The problem is that management sees them and says "oh, so we're finished with the project already? Yay!"