7 Scrum Team Mistakes--And How to Overcome Them

[@fruitloopygurl]

Fantastic video! I have witnessed all of these, and I’m glad you called out teams that want ALL details and questions resolved before beginning the work. That is just not always feasible- being comfortable with uncertainty takes practice 😊

[@MountainGoatSoftware]

It does indeed!

[@AndreiB2]

Tanks for the videos, Mike. ❤ Very well produced, crystalized and articulated!

[@MountainGoatSoftware]

Thanks, Andrei.

[@mikeanthony4000]

This is so informative. Thank you for sharing your experience and knowledge with us. Can you do videos on interviewing for questions and best possible answers. Thank you so much.

[@MountainGoatSoftware]

I'll add that to my "video backlog." Thanks!

[@mikeanthony4000]

@@MountainGoatSoftware thank you so much. I’m looking to get a job.

[@MountainGoatSoftware]

@@mikeanthony4000 Good luck with your job search. I do have a couple of blogs that may help. www.mountaingoatsoftware.com/blog/advice-for-interviewing-scrummasters and possibly: www.mountaingoatsoftware.com/blog/seven-tips-on-how-to-get-your-first-scrum-master-job

[@AndreiB2]

A very often made mistake is not injecting into the next Sprint improvement tasks discovered during the retrospective. The items are simply left there and forgotten.

[@MountainGoatSoftware]

Agreed. That is doubly frustrating--the team feels like they wasted time talking about things that won't be improved and then they're asked to do another retrospective to identify things that again will not be improved.

[@jonno946]

I've seen teams become disengaged with retrospectives because time is not given to carry out the remedial actions

[@MountainGoatSoftware]

Great point. If a team isn't going to act on the items selected in a retrospective, the retro feels worthless.