Are You a ScrumBut?

ScrumButs are defined as reasons why teams cannot take full advantage of Scrum to solve their problems and realize the full benefits of product development using Scrum. A ScrumBut retains the problem while modifying Scrum to make it invisible so that the dysfunction is no longer a thorn in the side of the team.

In his article, Bill Rinko-Gay provides different examples of ScrumButs attitudes:
* If your team reports its status to the ScrumMaster at the stand-up, you may be a Scrum-but
* If your developers keep getting ahead of your testers, you may be a Scrum-but
* If your team members are afraid to try new ideas because they might fail, you may be a Scrum-but
* If your retrospectives focus on who rather than what, you may be a Scrum-but
* If you insist on getting all of your stories defined in detail before you start your first sprint, you may be a Scrum-but
* If you focus on keeping to the original release plan, you may be a Scrum-but
* If you have to run all decisions through management, you may be a Scrum-but

And maybe the most important example is at the end: If you’re using this list to add rules and processes to your Scrum team, you may be a Scrum-but.

Read the complete article on http://www.scrumalliance.org/articles/483-you-may-be-a-scrumbut