Sliding Toward Success

You may have noticed we’ve been adding agile project management tools to the Mountain Goat Software website occasionally. We have a tool for calculating a confidence interval around your velocity data as well as various tools for prioritizing user stories or projects against one another. I’ve got a new tool to announce today—Project Success Sliders. Project Success Sliders were initially created and devised by Rob Thomsett in his book, Radical Project Management. Sliders are a way for a product owner (or collectively all key stakeholders) to convey expectations to the team. By default there are six sliders, each of which reflects some dimension by which project success can be determined—for example, delivery of all planned features, quality, meeting an agreed upon schedule. This can be seen in this figure:

These sliders are all balanced

Each slider starts at a value of three along a continuum from one to five. The product owner or key stakeholders then moves sliders up or down to reflect the appropriate mix of factors in determining the success of the project. Stakeholders are prevented from simply moving all sliders to five by a rule that that every movement up must be offset by a corresponding move down.

If sliders are out of balance (e.g., too many have been moved to higher numbers), the green checkmark in the upper right is replaced by a red circle and number showing how far out of balance the sliders are as you can see in this figure:

Sliders are out of balance

Sliders are brought back into balance when the product owner or stakeholders made additional adjustments to the sliders as shown in this example:

Sliders brought back into balance

Project success sliders can be a useful way to create an appropriate dialogue between stakeholders and team members about how success will be defined on the project.

Be sure to check out our Project Success Sliders tool.

Explore Further

Article artwork for 5 Key Factors for Effective Product Backlog Prioritization.
Article

5 Key Factors for Effective Product Backlog Prioritization

Featured

Confused about how to prioritize your backlog? These 5 factors will help to focus your efforts.

Article artwork for Product Backlog Refinement.
Article

Product Backlog Refinement

Featured

Learn about product backlog refinement: how, when, and why the agile team and product owner refine the product backlog in Scrum.

Text graphic: Keep the product backlog detailed appropriately.
Article

Make the Product Backlog DEEP

A DEEP product backlog is detailed appropriately, estimated, emergent and prioritized.

Article artwork for Four Steps to Keep Your Product Backlog Small and Manageable.
Article

Four Steps to Keep Your Product Backlog Small and Manageable

Reduce clutter so the backlog stays useful for prioritization and product decisions.

Article artwork for Why Your Product Backlog Should Look Like an Iceberg.
Article

Why Your Product Backlog Should Look Like an Iceberg

Shape the backlog so near-term items are detailed and lower-priority work stays lighter.

A definition of ready can be like a bouncer standing in front of a club. It blocks stories from entering the sprint and is a dangerous step towards a stage-gate process.
Article

Definition of Ready: What It Is and Why Its Dangerous

This post explains how to use a Definition of Ready successfully and avoid it becoming a first step back toward a waterfall process.