The Mountain Goat Software Blog

Boring retrospectives or ones in which people are afraid to speak the truth are just two of the most common problems with retrospectives.

Establishing a common baseline allows multiple teams to estimate consistently with story points.

Learn how product owners can evaluate refactoring when user-visible benefits are indirect.

Use questions to build trust, connection, and stronger collaboration across agile teams.

Get practical steps for landing a first Scrum Master role.

Use practical tips to make daily scrums shorter and 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.

Track buffer use to understand and manage interruptions during a sprint.

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.

Blog articles