Iron Triangle: Difference between revisions
Line 8: | Line 8: | ||
==Simply Put== | ==Simply Put== | ||
The notion that a product or service cannot be optimized in all of its aspects is a clear example of scarcity thinking | The notion that a product or service cannot be optimized in all of its aspects is a clear example of scarcity thinking. Such thinkng misses the point that open collaboration and development produces superior results. See [[Linux of Vaccines]] as a good and powerful example of breaking the iron triangle. OSE's [[Extreme Manufacturing]] and [[Extreme Enterprise]] models are examples where the Iron Trianle is smashed - with open collaboration. | ||
==Technicall Speaking== | ==Technicall Speaking== | ||
Extreme Manufacturing via modularity, collaborative design for optimization, modular breakdown, proper collaboration architecture, integration of desing-build-use-service issues by extremely tight coordination between these phases, open source, and test-driven design - beats the trilateral impossibility. | Extreme Manufacturing via modularity, collaborative design for optimization, modular breakdown, proper collaboration architecture, integration of desing-build-use-service issues by extremely tight coordination between these phases, open source, and test-driven design - beats the trilateral impossibility. |
Revision as of 22:24, 12 March 2021
https://en.wikipedia.org/wiki/Project_management_triangle
Good-fast-cheap - pick 2.
OSE Case
Simply Put
The notion that a product or service cannot be optimized in all of its aspects is a clear example of scarcity thinking. Such thinkng misses the point that open collaboration and development produces superior results. See Linux of Vaccines as a good and powerful example of breaking the iron triangle. OSE's Extreme Manufacturing and Extreme Enterprise models are examples where the Iron Trianle is smashed - with open collaboration.
Technicall Speaking
Extreme Manufacturing via modularity, collaborative design for optimization, modular breakdown, proper collaboration architecture, integration of desing-build-use-service issues by extremely tight coordination between these phases, open source, and test-driven design - beats the trilateral impossibility.