Shorter, focused events create better inspection, better adaptation, and higher engagement. Longer events that wander tend to do the opposite.

Being a great Scrum Master is all about balance. The Scrum Master coaches the team in self-management, but they also are responsible for helping the team focus on value by improving the adoption of the Scrum framework and removing organizational impediments. They ensure that the Scrum events are positive, productive and kept within the time box, but they don't have to attend every meeting.

One of the great things about Scrum that is not talked about enough is the fact that — done well — Scrum is an engine for continuous improvement.

If your AI has read-only access to your email, Teams messages, and calendar, try starting every morning with these questions:

When you modify Scrum, you’re usually hiding problems.

Sprint after Sprint, a lot of work remained unfinished at the end of the Sprint. Instead of returning that work to the Product Backlog or discussing next steps at the following Sprint Planning event, the vendor simply left the previous Sprint open. At any given time there might be four or five Sprints open for the same Scrum team. Don’t do this!