ScrumBUT teams have one common attitude, namely that they seem to be engaged in using Scrum… BUT… they have various excuses as to why some elements of the method have not been implemented.
This approach can be a really risky for all concerned, from the Management’s, the Product Owner’s and the team perspective. The Agile method promises to “Deliver greater value, more than before”, however by not applying practices appropriately can lead to failures, missed goals and deadlines.
Implementing Scrum the right way promises “Creating greater value for our customers, by speeding up time to market and becoming more Lean”. Scrum is a well defined method with a lot of practical guidance on how to use it. Each and every element plays an important role in becoming truly Agile, therefore by employing the “ScrumBUT” approach you risk not achieving success with Scrum.
Common reasons / excuses for the pick and mix approach to Scrum, include but are not limited to the following:
- Lack of knowledge or understanding of Scrum
- Insufficient resources
- No real commitment from leaders or team members
- Poor management structure
- Unclear, poorly defined goals
- Resistance against change in the structure and governance.
Some typical excuses why teams don’t implement Scrum perfectly:
We like Scrum, BUT we…
… like to vary the lengths of our Sprints according to the workload.
… don’t have daily stand-ups because we’re just too busy.
… don’t have sprint retrospective meetings. They’re not necessary.
… have the team manage the Product Backlog because the Product Owner can’t be bothered.
Most teams that intend to be Agile turn to Scrum. But unless you make the shift and become truly Agile, implementing Scrum won’t provide the performance gain that Agile is so well known for. Agile is about sticking to principles and is a lean framework, in other words it is a practical method for implementing those principles. Making the transformation to Agile requires following the rules and implementing the whole method correctly and sticking to those principles.
Employing ScrumBUT can lead to:
- Demoralization of teams
- More costs than benefits
- Less value, not achieved goals
Besides having a team with commitment and knowledge on board, we recommend using an Agile project management tool to guide you through the process of becoming truly Agile. codeBeamer ALM’s Agile Layer is available across the whole application, supporting Scrum teams in implementing Scrum fully and with minimal effort.