We get it, being a leader in the IT world is the hardest job to have. You are often caught between Practices and Policies that are not conducive to a good development environment. When everything goes south, the developers feel they are in a "Toxic Environment". If you, a developer; are there now, get out.
These are the attributes of a Scrum Master who is not a true leader.
- Expectations are over-the-top optimistic.
- They often ask "How'd we size this User Story so wrong?"
- Drill down charts are never looking good except maybe once or twice a year.
- They play dumb Retro team-building games like "If you were stranded on an Island...what music would you bring?"
- You as a developer feel that nothing you say really matters.
- You come out of retro meetings feeling irritated.
- Even with Planing Poker, your accomplishments never meet expectations.
- Collaboration? What collaboration?
There are more, but if you are seeing these things, you are officially in a can't win "Toxic Environment". It's probably best to start looking elsewhere to save your health and sanity.
BTW, none of these symptoms are the fault of the Scrum master wanting to make a difference and willing to collaborate with the worker-bees. Rather this is an issue with Upper Management.
JWP2019
Top comments (2)
The points you mentioned are so valid John. If the scrum master is rightly doing his job, he will be an example of true leader. Please note that I am not a practicing scrum master. Acquired the certification though. It really helped me in understanding what is really a scrum master. Most of the organizations still assumes that scrum master is a agile manager. I really wish they learn their lessons faster.
I do truly feel sorry for any Scrum master in the position described above. The root cause is usually either the corporate culture or the immediate upper management.
Good people go bad under too much pressure at all levels.