Unpopular Opinion
Welcome to the Unpopular Opinion community!
How voting works:
Vote the opposite of the norm.
If you agree that the opinion is unpopular give it an arrow up. If it's something that's widely accepted, give it an arrow down.
Guidelines:
Tag your post, if possible (not required)
- If your post is a "General" unpopular opinion, start the subject with [GENERAL].
- If it is a Lemmy-specific unpopular opinion, start it with [LEMMY].
Rules:
1. NO POLITICS
Politics is everywhere. Let's make this about [general] and [lemmy] - specific topics, and keep politics out of it.
2. Be civil.
Disagreements happen, but that doesn’t provide the right to personally attack others. No racism/sexism/bigotry. Please also refrain from gatekeeping others' opinions.
3. No bots, spam or self-promotion.
Only approved bots, which follow the guidelines for bots set by the instance, are allowed.
4. Shitposts and memes are allowed but...
Only until they prove to be a problem. They can and will be removed at moderator discretion.
5. No trolling.
This shouldn't need an explanation. If your post or comment is made just to get a rise with no real value, it will be removed. You do this too often, you will get a vacation to touch grass, away from this community for 1 or more days. Repeat offenses will result in a perma-ban.
Instance-wide rules always apply. https://legal.lemmy.world/tos/
view the rest of the comments
You haven't developed waterfall software have you.
No I haven't, but its better than finding out that you were supposed to make a mobile app on go-live day, instead of a website. Same basic functionality, but completely different front end.
That totally sucks. But has nothing to do with agile. That could have happened with waterfall because you would have sat there and developed things in isolation only to find out at the end it wasn't what was expected.
I guess thats true, but at least we would be able to point at a requirements doc instead of a mess of emails and messages.
That's the biggest problem with waterfall to be honest. You can sit there and point at requirements, but requirements can be interpreted differently. And that's a bigger issue with waterfall because you're handed a list of requirements with little context on what the purpose is of what you're doing because you weren't in any of the conversations earlier on in the process.
Agile doesn't mean you don't have requirements. What happened really sucks. But you aren't working in agile. You're just being screwed.
Yeah, maybe you're right. Just wish my lead pushed back more, and was a technical person. Probably would've stopped this train wreck before it began.