7 Scrum Team Mistakes--And How to Overcome Them

Inside "7 Scrum Team Mistakes--And How to Overcome Them"
Scrum isn't particularly hard. Yet agile team mistakes are common. Find out the 7 most prevalent missteps teams make when adjusting to an agile way of working. Learn agile team management tips to help overcome the obstacles that prevent teams from succeeding with agile.

Mike Cohn, author of three best-selling agile and Scrum books, introduces 7 Scrum team pitfalls and offers advice on how your team can escape them.

*******************
0:00 What new agile teams have in common
0:38 The #1 mistake teams make when they're new to Scrum
0:45 Scrum Master vs Manager
1:30 The biggest mistake teams make at their daily scrum
1:46 The purpose of the daily scrum
2:08 One way to help teams stop treating daily scrums as status meetings
2:18 The #1 thing Scrum teams do that makes it harder to be agile
2:57 Why uncertainty is OK at the start of a sprint
3:20 Mistake #4: Stories span multiple sprints
3:41 3 Things to Try when you are faced with user stories that are too big
4:34 Why unfinished sprint backlog items can be dangerous
4:51 What a sprint is meant to do for teams
5:25 How to break the habit of carrying work forward
5:48 The only thing worse than making mistakes in the first place
6:09 What to do if the team wants to skip retrospectives
6:18 Stop waiting for the retrospective to bring up issues!
6:41 What to do when an impediment can't even wait a day

Let's keep the conversation going. What other common mistakes has your team made? What's the worst mistake you've seen an agile team make? Let us know in the comments.

Don't forget to subscribe so you never miss future tips on how to succeed with agile.

[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 😊

[barmalini]

You make all of this look so easy, thank you

[AndreiB]

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

[mikeanthony]

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.

[AndreiB]

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.

[laurengoldsings]

Really interesting . As a new scrum master I thought having all the requirements, acceptance criteria and technical solution for US before the sprint was mandatory … I get now that it’s important to be ok with uncertainty, but how does the QA write all the tests while the developer is developing, if the ACs aren’t written ?

[jonno]

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