Is the title above sensational? I think the answer is yes. Was it intentional? Again, the answer is yes. Was the title unnecessary? I am sure the answer is yes. So why did I go there? For one simple reason: In most implementations, a lot of issues are blamed on Scrum. I thought it was time to give Scrum a sensationally positive headline.
Issues (impediments) are brought to the attention of the CSM for resolution. As the CSM starts to dig in, she finds most of the issues have been known within the organization for years. Scrum, with it’s desire for transparency, has put these issues under a magnifying glass for everyone to see. Here is a list of the types of issues that I have encountered:
- Lack of a defined intake process for work.
- Lack of understanding by functional and technical teams on what the other team does.
- The code promotion process outside the Sprint environments is not reliable.
- Developers think the testers take too long.
- Testers think the developers are cowboys.
- The DBAs agree with the testers. (see #5 above.)
- Team members don’t like or respect other team members.
- None of the team members trust management.
I am sure we could add a number of issues to the list. As I reflect back on the list, a number of them would be considered part of change management. As a Scrum coach or a CSM, you have to solve these impediments, as they jeopardize the current sprint, and maybe the adoption of Scrum. If you can’t solve the issues, then you can’t be successful. Solicit advice and get assistance from areas outside of your immediate Sprint team. Human Resources is always a good place to look for help and training. the appropriate resource managers to help.
Thanks for coning in today.