Symptoms of Manager Behavior in Scrum
Posted on August 27, 2010
Filed Under Scrum Basics | 1 Comment
While migrating from a traditional project management style to Scrum, often the old habits die hard. Especially for Managers, it is hard to stop doing something you have always done. Though the project is being executed as a Scrum, we find some of the traits of managers leaving a bad taste in the team, resulting in a complete failure. Its good to detect such behaviors early and correct it. Here are seven symptoms of a manager behavior in Scrum.
1. Command-and-control style continues – Manager continues to command and control the team like assigning activities, fixing deadlines etc.
2. Teams is lacking authority – Team lacks authority to make a valid point like unable to oppose any decision.
3. Scrum is “used”, but is not followed – Though Scrum is used, not all the rules are followed. Its more like a “Scrum But”
4. Managers exclude themselves from Scrum roles – Managers keep far from Scrum roles and responsibility
5. Invisibility and Passivity – Team being submissive and their voice not heard
6. Inability to tolerate failure – Failures are not tolerated
7. Not “Walking the talk” – Managers not doing what they advocate
8. Compliance without commitment – Agreement without any commitment
If you smell some or all of the above symptoms in your project, its time for some action and set things right
*Visited 2614 times, 1 So far today*
Comments
One Response to “Symptoms of Manager Behavior in Scrum”
Leave a Reply
-
About
All about Scrum Framework, Tutorials, Guides, Discussion Forum. KnowScrum.com is maintained by Scrum Certified Industry Experts. Please feel free to participate on Scrum initiatives on KnowScrum.com
-
Search
Great post I must say. Simple but yet interesting. Wonderful work!