Mountain Goat Software

Scrum has never had a design phase. Perhaps it’s time to fix that. Here’s a humorous take on how to do that.

Some agile teams ban certain roles from daily scrums and retrospectives. Here’s why everyone should attend, even the most difficult product owner.

We may think the Beatles simply sang about love, walruses and peace. But their songs actually contain profound agile lessons.

Being paid to do a job doesn’t make someone a professional. This post explains the crucial difference between an amateur and a professional.

A summary of Mike Cohn’s most popular and engaging blog posts of 2017.

Here are five key lessons I learned that were instrumental in my career. See if learning them could help your career, too.

A team’s sprints should be the same length every sprint. Here are four reasons why.

Read this special Halloween post about five things in agile transitions that are can seem as scary as any ghost or zombie.

User stories can be deliberately vague at first but detail needs to be added eventually. There are two ways to do that. Here they are.

What do the testers do at the start of a sprint when there’s nothing to test? That problem is solved through team collaboration.

How much authority must an agile team be given before it can be considered self organizing. And is self-organizing a better term than self-managing?

Even though not everyone may work on a product backlog item, it’s still worth having the full team estimate. Here’s why.