Articles on Scrum Events

Does your team's Sprint Planning seem like a complete and utter waste of time? Most of the time, the planning isn't the real problem.

The Scrum Guide says POs aren't required at Daily Scrum, but should they be? Explore why Product Owners should attend to increase team value.

Learn why Sprint Goals are essential for Scrum teams and how to create effective goals that drive focus and value. Includes examples and no best practices.

Daily Scrum is about improving communication, not status reporting

Product Backlog Refinement - Learn from my mistakes. From Boring to Valuable, all while taking less time

Good Scrum teams know that they own the Sprint Backlog. Great teams experiment.

From the Cambridge Dictionary, facilitation is “the act of helping other people to deal

Boring, Repetitive Retrospectives, create disengagement and lead to inaction

Replace Show and Tell with Show and Play. Saving Boring Sprint Reviews one Step at a Time

Sprint Planning is the most underappreciated Agile event, leading to errors and misunderstandings

Retrospectives are not Post Mortems. They're about your next tangible improvement

How long should a Scrum Sprint be? A Scrum Sprint is a short period of time when the

Hardening Sprints are one of the most common Scrum Anti-Patterns. They harm quality

More Work In Progress leads to less work finished

It is common in the early stages of Scrum implementation for there to be misunderstandings

The team doesn't understand that Daily Scrum is for them, not a management reporting tool.

No, of course not. So when should your Team start and end Sprints? The usual rules of

Continuous collaboration matters more than following a pre-ordained flow

Team members performed a play illustrating Story Splitting and INVEST

The longer we go without receiving feedback the more likely it is that there will be a problem

This question often comes up. Usually because a team has become bored with their

For the sake of simplicity, I’m ignoring anything beyond release planning (e.g. strategic,

There is no required format for DailyScrum.

This statement is a great start, but it doesn’t explain why or give you much guidance

Games that demonstrate process improvement, early delivery, small batches, and cross-functional benefits

At Agile 2007, I attended Jean Tabaka's (author of [Collaboration

Don't estimate task hours It doesn't work

Meetings need simple ground rules and a clear agenda