Why "Agile Scrum" is an oxymoronWhether you choose Scrum, Kanban, Lean or any other framework, if you only do that, you're not being agile.
Scrum is perhaps the best-known “Agile Framework”. So how can I get by saying “Agile Scrum” is an oxymoron?
Lest you think I’m picking on Scrum, let me expand my list of Agile oxymorons a bit:
- “Agile Kanban” is an oxymoron
- “Agile Lean” is an oxymoron
- “Agile XP” is an oxymoron
I could go on, but I think you get the picture.
And my point is this:
No matter which framework or methodology you choose, if you stick to that thing, you’re not being agile. And as soon as you are being truly agile, you’ll begin to diverge from the chosen framework or methodology, to the point that you’re no longer truly doing that thing.
How do I keep my devs busy while waiting on code review?
Don't worry about devs not having enough work. Worry on flow through the system.
Pick a methodology: Scrum, Kanban, XP, Lean or DevOps?
None of these items directly replaces or conflicts with any of the others. In fact, you can use them all simultaneously.
Improve your software delivery