The Mountain Goat Software Blog
Blog articles
Deciding What Kind of Projects are Most Suited for Agile
Agile is most appropriate on any urgent project with significant complexity and novelty--and that includes software development and weddings.
Should Story Points Be Assigned to a Bug Fixing Story?
My usual recommendation is to assign points to bug fixing the agile defects. This really achieves the best of both worlds.
The Problems with Estimating Business Value
Avoid false precision when estimating business value on small backlog items.
Story Points Estimate Effort Not Just Complexity
Clarify why story points estimate effort, not just technical complexity.
Sliding Toward Success
I’ve got a new tool to announce today—Project Success Sliders.
Managing Risk on Agile Projects with the Risk Burndown Chart
It is possible for risk management and agile project management to coexist on projects that need to explicitly do so.
Agile Teamwork
Learn how agile teams share responsibility, reduce handoffs, and finish valuable work together.
Nine Questions to Assess Team Structure
Use nine questions to assess whether your team structure supports agile collaboration.
Distributed Teams: Build Trust through Early Progress
Teams with subgroups formed around compatible skills, attitudes and approaches to work are less likely to lead to a later breakdown in trust.
Separate Estimating from Committing
Remember the difference between an estimate and a commitment and keep the two activities separate, educating management and customers as necessary.
Removing Team Members
People often ask me whether teams should have the right to vote members off. To help answer that question, let me share a story with you.
Build Trust Between Teams with Ambassadors
I’ve found that the personal relationships established by ambassadors can be extremely valuable even long after the ambassador returns to native soil.