9 Pitfalls of a SM to watch for

Get Started. It's Free
or sign up with your email address
9 Pitfalls of a SM to watch for by Mind Map: 9 Pitfalls of a SM to watch for

1. 1

1.1. Namesake SM

1.1.1. Cues

1.1.1.1. Agile Transformation - someone has to be SM

1.1.1.2. Anyone will do the job

1.1.1.3. Just get them certified

1.1.1.4. No experience - can't train experience

1.1.1.5. When met with obstacles - apply what they know best project management

1.1.2. Resolution

1.1.2.1. Pair with an experienced SM or Agile Coach

1.1.2.2. Bank on Agile Values and Principles

1.1.2.3. Give them time to learn - find mentors

1.1.3. Reflection

1.1.3.1. Have you been in this space?

1.1.3.2. Have you seen anyone/team suffer this dysfunction?

1.1.3.3. How would you deal with this situation?

2. 9

2.1. Scaredy-cat SM

2.1.1. Cues

2.1.1.1. In comfort zone

2.1.1.2. People pleaser, plays nice

2.1.1.3. Practical is safe and comfortable

2.1.1.4. Doesn't rock the boat

2.1.1.5. Mundane and boring Events

2.1.2. Resolution

2.1.2.1. Build Passion

2.1.2.2. Be disruptive - challenge the status quo

2.1.2.3. Fight for change

2.1.3. Reflection

2.1.3.1. Have you been in this space?

2.1.3.2. How did the team suffer?

2.1.3.3. What would you do in this situation?

3. 8

3.1. Absent SM

3.1.1. Cues

3.1.1.1. manages multiple teams

3.1.1.2. Mostly absent in events

3.1.1.3. doesn't pay attention to team dysfunctions

3.1.1.4. doesn't feel belonged

3.1.1.5. impediments persist

3.1.1.6. miss critical coaching moments

3.1.2. Resolution

3.1.2.1. Genuinely care for the team

3.1.2.2. Fully engaged, especially during crucial and critical times

3.1.2.3. Jump-starts a disengaged team

3.1.3. Reflection

3.1.3.1. Have you been in this space?

3.1.3.2. How did the team suffer?

3.1.3.3. What would you do in this situation?

4. 7

4.1. Policing SM

4.1.1. Cues

4.1.1.1. Micro-managing tasks, hours, points

4.1.1.2. Calls out violation of Scrum Guide all the time

4.1.1.3. Penalizes the teams

4.1.1.4. Fearful environment - people are afraid to fail

4.1.1.5. Expects Scrum teams to be PERFECT

4.1.2. Resolution

4.1.2.1. Understand it's difficult to execute perfect Scrum - strive for constant improvement

4.1.2.2. Experimental Mindset

4.1.2.3. Understand What Is and What Can Be

4.1.2.4. Set goals

4.1.2.5. Success is a journey not destination

4.1.3. Reflection

4.1.3.1. Have you been in this space?

4.1.3.2. How did the team suffer?

4.1.3.3. What would you do in this situation?

5. 6

5.1. Watermelon Syndrome SM

5.1.1. Cues

5.1.1.1. All green updates

5.1.1.2. Tech debt underlying

5.1.1.3. Covers mistakes to protect image

5.1.1.4. Emphasis on development being a Cakewalk

5.1.1.5. Craft illusion of perfection

5.1.2. Resolution

5.1.2.1. Find problems as early as possible

5.1.2.2. Embrace red for competitive advantage

5.1.2.3. Early modifications to address problems - tech debts

5.1.2.4. Transparent Sprint Reviews and other events

5.1.2.5. Don't be afraid to raise problems

5.1.3. Reflection

5.1.3.1. Have you been in this space?

5.1.3.2. How did the team suffer?

5.1.3.3. What would you do in this situation?

6. 5

6.1. Output Loving SM

6.1.1. Cues

6.1.1.1. Always focused on more output

6.1.1.2. Building more features

6.1.1.3. No measure of Value

6.1.1.4. Believes faster the output better the customer experience

6.1.1.5. Teams burn out

6.1.1.6. Miss customer delight

6.1.2. Resolution

6.1.2.1. Embrace customer outcome as driving force

6.1.2.2. Outcomes should dictate the focus

6.1.2.3. Happy teams - magic happens

6.1.3. Reflection

6.1.3.1. Have you been in this space?

6.1.3.2. How did the team suffer?

6.1.3.3. What would you do in this situation?

7. 4

7.1. Order-giver SM

7.1.1. Cues

7.1.1.1. Tells the them what, when, and even how

7.1.1.2. Feels in charge

7.1.1.3. Tries to take control

7.1.1.4. Team is always dependent on SM to guide them

7.1.1.5. Always has answers/solutions to everything

7.1.2. Resolution

7.1.2.1. Coach to release command-and-control

7.1.2.2. Ask the team for solutions

7.1.2.3. Problem solving is a muscle - you can train it

7.1.2.4. Help build autonomy

7.1.2.5. Mantra - Let the team decide

7.1.3. Reflection

7.1.3.1. Have you been in this space?

7.1.3.2. How did the team suffer?

7.1.3.3. What would you do in this situation?

8. 3

8.1. Order-taker SM

8.1.1. Cues

8.1.1.1. takes orders unconditionally

8.1.1.2. Cannot protect the team

8.1.1.3. Their bosses give orders - they take it

8.1.1.4. Always serving other's needs

8.1.1.5. No autonomy, No self-managed teams

8.1.2. Resolution

8.1.2.1. Give autonomy to teams, let them self-manage

8.1.2.2. Protect the teams - be their shephard

8.1.2.3. Should learn to say NO

8.1.2.4. A SM who can say no to orders is a thousand times worth than the one who only takes orders and says YES

8.1.3. Reflection

8.1.3.1. Have you been in this space?

8.1.3.2. How did the team suffer?

8.1.3.3. What would you do in this situation?

9. 2

9.1. Misguided SM

9.1.1. Cues

9.1.1.1. Build bad Scrum/Agile habits

9.1.1.2. Not ready to unlearn

9.1.1.3. Setting team Stretch Goals

9.1.1.4. Using Velocity as assessment metric

9.1.1.5. Measuring committed vs actual points/hours

9.1.1.6. Team Engagement Suffers

9.1.2. Resolution

9.1.2.1. Firstly, look for right talent

9.1.2.2. Warning signs

9.1.2.3. Avoid SMs who squeeze every ounce of efficiency of team members

9.1.2.4. Seek SM that embrace learning and improvement path to greatness

9.1.3. Reflection

9.1.3.1. Have you been in this space?

9.1.3.2. Have you seen anyone suffer?

9.1.3.3. What would you do in this situation?