Optimizing the success of an agile project

When is a good time to stop your agile project?

The goal of this article is to provide the reader with a range of tools, processes and practices in order to understand that a point exists in time, after which further development becomes a waste of time and resources.

When to stop an Agile development project and call it a day? When are the minimum number of requirements implemented to guarantee customer satisfaction within an optimal budget?

It definitely takes courage to stop a project when there are still user stories on the sprint backlog.

However, there are several theories and studies that support agile project managers in making the right decisions.

Here are a few that I find most interesting to consider …

80/20

Image for post
Image for post
The Pareto principle

In order to implement 100% of the requirements, you need to spend five times the amount of time needed to implement the first 80% of the requirements.

Will it be worthwhile to implement the remaining 20% ? Maybe, but it’s at least very wise to question this before moving forward….

The law of decreasing value

This is shown in the following graph:

Image for post
Image for post
After moment ‘x’ the resulting value of the task decreases.

‘x’ marks the ideal (theoretical) moment in time to stop this particular task as, up to this point, it provides the most optimal value/time ratio.

The Sprint Cost

If the product owner doesn’t care, maybe the business owner or stakeholder does…

If you plan to use this metric in your projects, you should communicate and apply it from the beginning. You need to agree from the start that the sprint cost is an important element to consider when determining the business value of a sprint.

The role of the Product Owner

To summarize

This is summarized in the graphic below:

Image for post
Image for post

As of sprint x+2, the value delivered by the sprint is not larger anymore than the sprint cost.

People should start wondering whether it makes sense to continue the project beyond this point, and whether starting sprint X+3 is still justified from an economical point of view.

The ratio V/C stands for Value/Cost. From a pure mathematical point of view this ratio should ideally be >1, as this means that the sprint produces more value than its cost.

In a future post, I will write about how to determine the V/C ratio. In other words, how to define the economical value of a requirement.

Stefan Luyten

For more information: http://www.triton-consulting.be

Written by

Enterprise & Solutions Architect consultant.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store