3 ms·
I've been on 5 or 6 different teams that used what they called scrum. I've never seem it work well, either it quickly devolves into an exercise in going through
by _heimdall 2y ago
I've been on 5 or 6 different teams that used what they called scrum. I've never seem it work well, either it quickly devolves into an exercise in going through the motions or it's used as a micromanagement exercise on a team with little trust.
I have seen it occasionally help promote better communication within the team, like earlier calling out dependencies or having team members ask for help earlier. Communication is a different challenge though, scrum is too oppressive when the problem to solve really is just better, and more frequent, communication on a team.
- vundercind 2y agoI’ve seen it used well in a small (3-4 team) dev shop. But its value was almost entirely in managing clients, not developers, and it required absolute buy-in from the whole org, owners down. If our clients had been above us in the org chart, it would have fallen apart, or at best just slowed things down while making everybody more stressed out.
- skydhash 2y agoIt can be great that way. And it’s generally useful when the objectives of the teams are not the consulting business, but the client. Meet every two weeks to discuss the project and get feedback on what’s been done. Often, it’s not the devs doing the meeting. But scrum inside a business is pretty much a nightmare scenario.
- ruzig 2y agoScrum is to protect the team. The team just works at their cadence, and the velocity will help the team not commit too many points for the next sprint. The communication is the same with Kaban; I didn't see any difference.