Iterating changes to processes
Just like with application code, it is important to take an iterative approach to changing processes. When it comes to application code, we take this approach so that if something does go wrong, we can easily know what changes were made, who made them, and why. It provides full traceability of what is happening.
We need that same level of traceability and transparency when it comes to iterating changes to processes. That way, if at any point we need to see what happened and why, it's easy to identify that information. Secondly, we can see the impact of a change before moving onto the next one.
This really applies to all types of changes, from technology processes to business processes. The biggest impact does not come with individual changes to those processes, but large programs of change that involve numerous changes to the same set of processes or the same process.
When we work in iterations, or in sprints as we commonly call them in...