The Mountain Goat Software Blog

Blog articles

Scrum team looking at a screen with popcorn, movie ticket, directors marker and soda.

Does a Scrum Team Need a Retrospective Every Sprint?

Decide how often retrospectives should happen based on sprint length and team needs.

Article artwork for Can a Traditional SRS Be Converted into User Stories?

Can a Traditional SRS Be Converted into User Stories?

Decide when an SRS can inform a backlog and when rewriting it into stories helps.

Article artwork showing a zero-point Planning Poker card on a product backlog board.

Should You Use Zero-Point Estimates on Your Product Backlog?

Understand when a zero-point estimate is useful and when it hides real work.

Article artwork for Leave Work Unassigned and See Who Steps Forward.

Leave Work Unassigned and See Who Steps Forward

Encourage ownership by leaving work unassigned and seeing who steps forward.

Article artwork for Who Can Add Items to the Product Backlog?

Who Can Add Items to the Product Backlog?

Clarify who can add backlog items and how product owners keep control.

Text graphic: Ask better questions when choosing a Scrum Master.

Advice for Interviewing ScrumMasters

Ask better questions when hiring or evaluating Scrum Master candidates.

Text graphic: Balance design discovery with sprint delivery.

Incorporating UI Design in Agile Sprints

Integrate UI design into sprints while balancing discovery and delivery.

Article artwork for Handling Work Left at the End of a Sprint.

Handling Work Left at the End of a Sprint

Decide what to do when sprint work is unfinished.

Article artwork for An Iterative Waterfall Isn’t Agile.

An Iterative Waterfall Isn’t Agile

Spot when sprints are masking a waterfall process and how to move toward real agility.

Text graphic: Question the numbers before they become product folklore.

Are 64% of Features Really Rarely or Never Used?

Understand the often-cited “rarely used features” statistic and what product owners should take from it.

Text graphic: Split stories for clarity, not arithmetic perfection.

Estimates on Split Stories Do Not Need to Equal the Original

Understand why split story estimates do not need to add up to the original.

Article artwork for Not Everything Needs to Be a User Story: Using FDD Features.

Not Everything Needs to Be a User Story: Using FDD Features

Know when FDD-style features may work better than forcing every item into a user story.