akurganow/toc-thinking

Find the core problem behind many symptoms in a software system with Goldratt's Theory of Constraints Thinking Processes. Then resolve the conflict that keeps it in place, and plan the change with its obstacles named. Use when symptoms are many and the cause is unclear, or when the same failure keeps coming back. Use when two requirements block each other. Use when a migration needs a plan, or when a proposed change needs checking before it is built. Scrutinise each sufficiency tree with the published Categories of Legitimate Reservation, and each necessity arrow by its assumption.