The Mountain Goat Software Blog

In a recent weekly tip, I offered six tips on making the daily scrum more useful but I couldn't stop at six. Here are ten more tips to help make your daily scrum more useful.

As useful as user stories can be, they’ve never been right for every team. An exciting alternative for some teams is the job story.

For many teams, the sprint review has run its course and it’s time to stop doing them. Blasphemy? Maybe, but hear me out.

In an ideal world, a Scrum team could perform the work of its sprints entirely uninterrupted. Product owners would never introduce change. Customers would never request urgent new functionality. And users would never discover any defects. While teams can aspire to a world of no sprint interruptions, it is not the world in which most teams operate. Most Scrum teams do have to deal with interruptions of these types.

Do Scrum long enough and someone will suggest stopping the daily scrums. Here’s how to reply.

When estimating in story points, teams should think in terms of ranges and rounding up. Here’s why.

Batman would make the perfect Scrum Master. Once he eliminates crime in Gotham City, I plan on offering him a job. Here’s why.

It can sometimes be a challenge to get people to attend and then participate in sprint reviews. Here is advice on overcoming that problem.

From helping teams understand the boundaries of self organization to creating safety around things like estimates and mistakes, here are six things teams want from their Scrum Masters.

Your team is probably spending too much time in sprint planning meetings. Here’s how to spend less time but plan better.

Debating between Scrum and Kanban? Guest author Brendan Wovchko offers five advantages Kanban has over Scrum.

Most individuals know that multitasking slows us down. It has an equally negative effect on agile organizations and teams.