DevOps Transformation using Theory of Constraints

Very good and comprehensive article. But there is one thing that Dr. Goldratt always pointed out, one step is missing there. Step 5 is to reflect on the change after it happens. That is what makes the process continuous. There always has to be a reflection as the result of reflection is either a feedback from a failure of the idea (to execute or to achieve actual positive result) or a new idea (to either improve on the current change or for another change). Even if all the previous steps were correct and executed correctly, without reflecting on the process, you lack both the knowledge of success or failure and the new ideas generated out of the reflection. Further the itself reflection has to be a part of the original idea. It has to be defined ahead of execution as ex post facto reflection tends to redefine the original goals to fit the achieved results.

Show your support

Clapping shows how much you appreciated Jiri Klouda’s story.