Optimisation is Iteration Done Right
Legacy…every system which is designed and implemented should be considered legacy at the moment of inception. This notion is supported by the fact that Technology and Process changes tend to expose systems to the need for immediate maintenance.
Maintenance of a system is carried out in an iterative manner with the end goal of producing small changes that result in impact. In the Agile world, these small changes are managed and allocated into their specific sprints. A sprint in the Agile world is a short, defined period of time usually 2 weeks in which a small subset of issues are dealt with.
The problem with this is that once a system is in operation, the majority of the tasks dealt with, within a sprint often address bugs and small fixes (fixing current thinking) which doesn’t produce any real measurable outcome. This gives the perception of attaining optimisation when in fact it is simply maintaining the status quo.
Optimisation is the improvement of a system almost to the point of ‘perfection’ which can produce a measurable outcome both in terms of system performance and a subsequent reflection on the bottom line. It is the introduction of new thinking and staying ahead of the curve that truly achieves Optimisation.
How much of the operational time budget is allocated to true Optimisation.
If iteration is truly going to mean anything, a greater majority of the tasks that are prioritized, need to inform optimisation rather than iteration for the sake of iteration.
If you like this article please hit the ❤️.