this post was submitted on 06 Jun 2024
476 points (89.3% liked)
Technology
59605 readers
3366 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
That's because they forgot the meaning of the word agility and want to apply the rules what ever the cost
And also because it's a comfortable cover up for any kind of money saving stupidity. We don't need proper requirements engineering, we're agile. We don't need an operations team we're doing an agile DevOps approach. We don't need frontend Devs, we're an agile team you all need to be full stack. I have often seen agility as an excuse to push more works towards the devs who aren't trained to do any of those tasks.
Also common problem is that still tons of people believe agile means unplanned. This definitely also contributes to projects failing that are just agile by name.
100% my experience.
Especially the last part. Writing a single word into a jira ticket doesn't make it a story, epic or sub task. You're too lazy to specify, that's not what agile is meant to be.
I don’t know how many times I have been waiting for the product manager to get out of their meeting so they can help me clarify what they really mean with their "high priority" ticket only consisting a vague title.
"Looks like I'm home early, bye"