The Mountain Goat Software Blog

Understand the three kinds of requirements teams need to consider.

Sprint goals are considered a mandatory part of Scrum. Here’s why I disagree.

Clarify what cross-functional teams really need and what they do not.

See what teams and Scrum Masters need most from a product owner to make delivery smoother.

Learn the qualities that help Scrum Masters serve teams effectively.

Succeeding with Scrum is easier when you know when and why to conduct each of the Scrum events during the sprint.

Understand what story points measure and why they are often misunderstood.

Story points are about time, specifically effort. But that does not mean you should say, “One story point = eight hours.” Find out why.

Write non-functional requirements in ways teams can discuss, estimate, and test.

Clarify the difference between epics, features, and user stories without getting stuck on labels.

Transitioning to Scrum is worth it, but some aspects are challenging.

Compare user stories with requirements and use cases to see where stories help agile teams.

Blog articles