Learn how to Slide through to Success!

by Matt Francis, Apr 04, 2018

At WorkingMouse we want our Partners to succeed in achieving their goals. Embarking on the journey of building software can be quite daunting and WorkingMouse encourages everyone to take a Sanity Check before diving straight in to development of a software application.  We also implement a range of tools and processes in order to ensure the smoothest development process possible.
One of the most useful tools WorkingMouse uses during the development process is a Success Slider. First coined in Rob Thomsett's brilliant book "Radical Project Management", the concept refers to a tool used to help all project stakeholders agree on the success criteria and priorities of a task. At WorkingMouse we use Success Sliders as a way to educate our Partners and enable them to collaborate with their assigned project teams in order to come to a shared understanding about how the project will be measured as successful on completion. The general rule that applies to all Success Sliders (not just the WorkingMouse variation) is that they cannot all be "fixed". If this was to be allowed it would be an immediate indicator that the project will fail to meet expectations for both the developer and partner.
So how does a WorkingMouse Success Slider work? We ask our Partners to consider the value they place on four criteria: scope, cost, time and quality. Participating in this discussion allows our Partners to determine what their priorities are for the project development. We then ask our Partners to shade one box per row and per column of the Success Slider table, based on how fixed or flexible their expectations are for each criteria. Below is an example of what we consider to be the optimal choice for successful software development, however ultimately the Partner can decide their own priorities. 

The reason only one box can be shaded in each column and row is Newton's Third Law of Motion: for every action, there is an equal and opposite reaction. If the cost of the build is fixed for example, the quality is not necessarily reduced but the requirement for flexibility on quality increases. Another example is if the Scope of the project was fixed then by default one of the other three options (Cost, Time or Quality) will need to be more flexible. 
There is a general tendency with product owners (specifically for software), to regard all four categories as most important. However, utilising this tool provides WorkingMouse with a way to ensure key project stakeholders or product owners convey their expectations to the project's development team early on in the development process. This helps WorkingMouse make decisions in the event of a problem or conflict. It also ensures Partners understand the nature of trade offs and prioritisation.

If you would like to learn more about how WorkingMouse develops awesome software for our Partners check out our Whitepaper. If you are interested in developing with us, please take a couple of minutes to fill out our 4 question Software Readiness Form.