Iron Triangle: Difference between revisions
Jump to navigation
Jump to search
| Line 6: | Line 6: | ||
=OSE Case= | =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, that misses that open collaboration and development produces superior results. See [[Linux of Vaccines]] | |||
==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:19, 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, that misses that open collaboration and development produces superior results. See Linux of Vaccines
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.