I haven’t read your post, but I agree with your comment. There’s Scrum-but and then there’s Scrum. I’ve seen so many shitty implementations of Scrum, all because people don’t understand the why behind it.
As a bonus, if you understand the why behind Scrum, you can actually do non-Scrum stuff that’s perfectly Agile! A perfect example you already mentioned: Kanban. Or whatever.
The point is that there’s a set of problems that teams will always need to solve. Scrum is one way. It’s not the only way.
Yeah, this is probably going to sound like a truism, but to avoid shitty Scrum, you need to resist management trying to alter the processes, but you should absolutely tweak the processes to account for the needs of the devs.
Basically, yet another reporting meeting does not help deliver the software faster. But more (or less) meetings for devs to sync what they’re working on, that can help, depending on your team’s specific needs.
I haven’t read your post, but I agree with your comment. There’s Scrum-but and then there’s Scrum. I’ve seen so many shitty implementations of Scrum, all because people don’t understand the why behind it.
As a bonus, if you understand the why behind Scrum, you can actually do non-Scrum stuff that’s perfectly Agile! A perfect example you already mentioned: Kanban. Or whatever.
The point is that there’s a set of problems that teams will always need to solve. Scrum is one way. It’s not the only way.
Yeah, this is probably going to sound like a truism, but to avoid shitty Scrum, you need to resist management trying to alter the processes, but you should absolutely tweak the processes to account for the needs of the devs.
Basically, yet another reporting meeting does not help deliver the software faster. But more (or less) meetings for devs to sync what they’re working on, that can help, depending on your team’s specific needs.