So glad you asked! Years ago I spent some time with the Theory of Constraints hoping to apply it to application development. The basis is actually two different things.
1. Theory of Constraints: According to www.focusedperformance.com:
It is based on the fact that, like a chain with its weakest link, in any complex system at any point in time, there is most often only one aspect of that system that is limiting its ability to achieve more of its goal. For that system to attain any significant improvement, that constraint must be identified and the whole system must be managed with it in mind.
Once the constraint is identified, operational management focuses on optimizing use of the constraining resource. All other resources are subordinated to the constraining resource. This works best when the constraining resource can be identified and then does not change very often. (There may be techniques for when the constraint changes often but that is beyond my knowledge.)
2. Thinking Tools: Problem-solving techniques that focus on cause and effect as well as sufficiency and necessity. (What things are necessary and sufficient to make a certain outcome come to pass? Necessary: the prerequisite _must_ be in place. Sufficient: if the prerequisites are in place, then the outcome _will_ come to pass.) It uses graphics (trees which display cause and effect) and clouds (which display basic conflicts between what exists (the problem) and what we want to happen).
As you can see the Theory of Constraints and the Thinking Tools are applicable to more than manufacturing.
From: erp4it@yahoogroups.com [mailto:erp4it@yahoogroups.com] On Behalf Of Charles Betz
Sent: Saturday, November 22, 2008 10:46 AM
To: erp4it@yahoogroups.com
Subject: [erp4it] Assembling an MRP library
Sent: Saturday, November 22, 2008 10:46 AM
To: erp4it@yahoogroups.com
Subject: [erp4it] Assembling an MRP library
(snip) The Goal is of course a notable manufacturing novel. But what underlies it? What is the Theory of Constraints? (snip)