No Bad Scrum
One of the things I strive for in my work is to make sure that when people are doing Scrum, they are really doing it. My reasoning is that if you are going to go through all the effort and extra burden of Scrum, you might as well do it right and then decide if it is worth it. Unfortunately, in the course of my time helping teams implement Scrum I have seen a lot of what I would call “bad Scrum” and teams jettison the process without really doing (most of) it. Here are the common anti-patterns I have come across in the last year.
“We are doing Scrum, but …”
- “… we don’t have a Product Backlog.”
- “… the Product Owner does not prioritize our work.”
- “… our manager tells me what to do.”
- “… our ScrumMaster tells me what to do.”
- “… the only thing we do is fill out the Excel spreadsheet .”
- “… we don’t meet everyday ’cause we all work right next to each other.”
- “… we don’t do Retrospectives.”
- “… I just email my status to the ScrumMaster.”
- “… there are too many meetings. Can we cut some of the meetings?”
- “… it does not improve the quality of our product.”
- “… it still feels like business as usual.”
- “… no one removes obstacles.”
