The Mountain Goat Software Blog

Too often, agile teams are expected to finish everything every iteration. This expectation is harmful and wrong. Here’s what to do instead.

When a product backlog becomes too big, it hinders agility. Discover four steps your team can take today to reduce the size of your product backlog.

Pervasive myths about agile get in the way of success. It’s time to bust six of those myths.

The iterative and incremental nature of agile makes an agile approach seemingly less compatible with project governance or oversight. Traditional, sequential approaches to project management are a more natural fit with management’s desire for oversight on projects.

How to adjust velocity for holidays and time off.

Here’s what to do when facing a complex user story that cannot be split but is too large for one sprint.

A lot of organizations claim to be agile. Here’s a quick way to see if they really are.

Traditionally managed projects begin with a kickoff meeting. Here’s why and how agile projects can do the same.

It’s important for most agile teams to estimate both their product and sprint backlogs. But why?

An agile product backlog should evolve over time, with product backlog items and user stories rising toward the top according to priority. Learn how your team can make this happen.

Are you struggling to find a catchy name for your agile team? Use this fun, mostly silly, generator to find the perfect nam

Telling a stakeholder you can’t work on their feature is difficult. Here are ways to make that conversation easier.