The Sprint Retrospective, or “Retro,” is a Scrum Event that occurs at the end of every Sprint. During this Event, the Scrum team talks about the previous sprint – what went well and what can be improved – and then adapts their team processes, based on what is uncovered in that discussion. It is this consistent cycle of inspection and adaptation that creates a high-performing team. Unfortunately, this is the one Scrum Event that many teams (or worse, leadership) want to skip. However, I am begging you: Please. Do. Not. Skip. The. Retro. Seriously. Don’t do it!

One of the hardest things for the Scrum Master to do is to get team members to show up and participate in meetings. One way to combat this is to provide incentives to your Scrum team.

As Scrum Masters, we need to help our organizations identify and work through "bottlenecks". We first identify what these blockers are, then prioritize each item and tackle the highest impact items first.

I think of Scrum Backlog prioritization as if it is a restaurant experience. The backlog itself is a menu arranged to fit the customer’s needs.