Inherent simplicity vs apparent complexity

 

While it is important to understand that software development is not fully predictable I believe the approach many take with complexity is misguided.

If we can take actions in complex systems that predictably make things worse we can take actions that make them predictably better.

Theory of Constraints puts forward the concept of inherent simplicity-the presumption that inherent in complex systems are rules that, when understood, enormously simplify the system. These rules already exist. We must find them and take advantage of them. Doing so enables us to increase performance and reduce or eliminate the challenges we are facing.

I have been calling these natural laws, but now prefer ToC’s label because they may not be well-defined laws but noting them still enables us to see what to do. Some of these are:

• Small batches are better than large ones
• The system people are in greatly affects their behavior
• Delays in workflow and feedback create extra work to be done
• People's efficiency drops as the # of value streams they are in increases.
• You can’t manage what you can’t see
• Delays are caused when people do not collaborate
• Working beyond capacity creates waste
• Poor code quality creates unpredictability