Principles of Extreme Development: Difference between revisions

From Open Source Ecology
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
Extreme Development is the process of developing designs for [[Extreme Manufacturing]] (XM). The XM page already lists 11 tactical principles. Here we step out to a matalevel - so more judgment is required. Keeping the metaprinciples in mind is part of test-driven development - in that these metaprinciples allow for testing one's approach.  
Extreme Development is the process of developing designs for [[Extreme Manufacturing]] (XM). The XM page already lists 11 tactical principles. Here we step out to a matalevel - so more judgment is required. Keeping the metaprinciples in mind is part of test-driven development - in that these metaprinciples allow for testing one's approach.  
 
=Meta of Extreme Development - Approach Notes=


*Focus on [[Test Driven Design]] of Extreme Manufacturing.
*Focus on [[Test Driven Design]] of Extreme Manufacturing.
*Has this been proven in industry standards? If not, why not?
*is this technology in common use? If not, why not?
*Is there a risk that this will not work? Proceed only when that risk is negligible, otherwise find out more to proceed on an informed path.
*Has prior work been done by others? Are you aware of all the work? If not, what are some easy validations that you could do to find out more?
*Who are other stakeholders interested in this question?
*Have you communicated your development path, if that path is committed/serious - to the rest of the world?
*How is this leading to the fundamental solution of pressing world issues?
*What is the unique value proposition?

Revision as of 13:40, 13 January 2016

Extreme Development is the process of developing designs for Extreme Manufacturing (XM). The XM page already lists 11 tactical principles. Here we step out to a matalevel - so more judgment is required. Keeping the metaprinciples in mind is part of test-driven development - in that these metaprinciples allow for testing one's approach.

Meta of Extreme Development - Approach Notes

  • Focus on Test Driven Design of Extreme Manufacturing.
  • Has this been proven in industry standards? If not, why not?
  • is this technology in common use? If not, why not?
  • Is there a risk that this will not work? Proceed only when that risk is negligible, otherwise find out more to proceed on an informed path.
  • Has prior work been done by others? Are you aware of all the work? If not, what are some easy validations that you could do to find out more?
  • Who are other stakeholders interested in this question?
  • Have you communicated your development path, if that path is committed/serious - to the rest of the world?
  • How is this leading to the fundamental solution of pressing world issues?
  • What is the unique value proposition?