The Mountain Goat Software Blog

Plan sprints using velocity while understanding its limits.

Define quality in a way that helps agile teams make better tradeoffs.

Understand why teams use story points instead of hours or days.

Use specialists wisely without letting them become bottlenecks.

Use short release cycles to learn faster, reduce risk, and improve the product sooner.

Pick backlog items that deliver value while helping the team learn what matters next.

Add context to user roles so stories describe needs with more precision.

Find the pace where teams move quickly without losing control.

See why developers should help write user stories before work reaches the sprint.

I recommend using Planning Poker on product backlog items rather than on the tasks that make up a sprint backlog.

Use focus and presence to improve collaboration, meetings, and team performance.

Connect product vision to backlog decisions so teams build toward a product customers actually want.

Blog articles