Why is Scrum being forced onto non-Agile teams?
Newly integrated teams are forcing a rigid Scrum approach onto projects requiring traditional or hybrid methods, refusing feedback from existing staff. This creates friction, hostility, and widespread frustration instead of productivity, resulting in excessive meetings that stall work.
What people tried
Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.
- 1Continuing to use waterfall to actually plan projects while using Agile buzzwords in meetings
- 2Flipping the script back to the project board, sponsor, or executive using project controls
- 3Refusing to adopt the new process based on niche expertise
- 4Leaving the organization or waiting for the process to implode over time
In their words
Unedited, most upvoted first, each linked to the thread it came from.
“It has made for a rough experience for all involved and not everyone has bought into the process.”source ↗
“When I have attempted to provide that feedback, they basically refuse to acknowledge any of it and are continuing to force their process onto everyone else who works on projects which has resulted in frustrations and some hostility between our teams.”source ↗
“Rather than twice the work in half the time, you get half the work and twice the meetings.”source ↗
Where this came up
People with this problem also raised
- 7How to survive a completely mismanaged project with terrible leadership
- 2How to handle project management and coding at the same time
- 5How do I deal with non-technical managers and constant interruptions?
- 20How to deal with uncooperative coworkers who don't do their work
- 6Should I trust the contractor who disagrees with everyone else?
- 5Why do other departments ignore accounting policies?