If you’re using agile you should use it all, no exceptions. ScrumBut is bad. In general you can’t be somewhat agile. You either fully are or are not at all. You must see that a lot around the interwebs.
Sorry guys, but even with all these old-school heavy-weight highly-processed methods you are told most of things are optional and you should use those which are relevant to your situation. I understand the difference – if RUP describes more than 120 rules you aren’t supposed to follow them all, if Scrum ends up with less than 10 each of them is probably much more important on average.
Yet still when I see Kanban with barely 3 rules I’m ready to skip one if I believe I don’t need it at the moment. You can tell I’m neither agile nor lean and you know what? That’s fine. That’s perfectly fine because I don’t care about labels.
And I’m not alone here. Exception-powered Scrum, also known as ScrumBut, is pointed as the best part of Scrum almost as frequently as a major sin. I’m not surprised. I believe every methodology or approach should be treated as a toolbox. You choose the tool or tools which suit you fine at any given moment. If something generates only additional hassle and bring no value you just put it back to the box.
By the way, there isn’t even clear definition what does it mean to be fully agile. Is Scrum implemented by the book agile or not yet? Do you have to follow XP to call yourself agile? And who said that after all?
My take is: you can perfectly be somewhat agile. You can just use few of Scrum techniques and I’m fine with it. What makes difference at the end of the day is not which practices you did use but whether software is high-quality or not. And believe it or not people were building high-quality software long before agile was coined-up.
All posts of The Carnival of Agile Bullshit.