Principles of Extreme Development - Revision history

Marcin: /* Meta of Extreme Development - Approach Notes */

2016-01-13T14:51:28Z

Meta of Extreme Development - Approach Notes

← Older revision		Revision as of 14:51, 13 January 2016
Line 18:		Line 18:
	*Have you communicated your development path, if that path is committed/serious - to the rest of the world?		*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?		*How is this leading to the fundamental solution of pressing world issues?
	*~~What is the~~ unique value proposition?		*Do you have a clear and unique value proposition and vision that can excite people?
	*do you have a clear statement of goals?		*do you have a clear statement of goals?
	*do you have a clear statement of scope? I've, do you have a clear go and no-go list of things you are willing to engage in?		*do you have a clear statement of scope? I've, do you have a clear go and no-go list of things you are willing to engage in?

Marcin: /* Meta of Extreme Development - Approach Notes */

2016-01-13T14:48:18Z

Meta of Extreme Development - Approach Notes

← Older revision		Revision as of 14:48, 13 January 2016
Line 7:		Line 7:
	*what revenue model makes this sustainable and scalable for the future?		*what revenue model makes this sustainable and scalable for the future?
	*Do you have a critical path and contingency plan?		*Do you have a critical path and contingency plan?
			*has your current work been categorized consciously as a top priority? Are you following a conscious sequencing in the short and long term?
	*Do you have a team and budget? If not, how will you build a team and fund the development?		*Do you have a team and budget? If not, how will you build a team and fund the development?
	*Do you have a roadmap, a stable process, development protocols, and documentation protocols to offer a clear path of development?		*Do you have a roadmap, a stable process, development protocols, and documentation protocols to offer a clear path of development?

Marcin: /* Meta of Extreme Development - Approach Notes */

2016-01-13T14:45:30Z

Meta of Extreme Development - Approach Notes

← Older revision		Revision as of 14:45, 13 January 2016
Line 10:		Line 10:
	*Do you have a roadmap, a stable process, development protocols, and documentation protocols to offer a clear path of development?		*Do you have a roadmap, a stable process, development protocols, and documentation protocols to offer a clear path of development?
	*Is your pen mightier than the sword - ie, is thinking preceding action, or is the action not well-directed?		*Is your pen mightier than the sword - ie, is thinking preceding action, or is the action not well-directed?
	*Has ~~this~~ been proven in industry standards? If not, why not?		*Has the technology that you are developing been proven in industry standards? If not, why not?
	*is this technology in common use? If not, why not?		*Is this technology that you are developing 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.		*Is there a risk that your build/design will not work? What is that risk? 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?		*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~~?		*Who are other stakeholders interested in the questions/development that you are doing? How do you find them? Before you find them, how do you send the right message to make sure that they are aligned?
	*Have you communicated your development path, if that path is committed/serious - to the rest of the world?		*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?		*How is this leading to the fundamental solution of pressing world issues?

Marcin: /* Meta of Extreme Development - Approach Notes */

2016-01-13T14:42:45Z

Meta of Extreme Development - Approach Notes

← Older revision		Revision as of 14:42, 13 January 2016
Line 6:		Line 6:
	*Are you pursuing [[Test Driven Design]] of Extreme Manufacturing.		*Are you pursuing [[Test Driven Design]] of Extreme Manufacturing.
	*what revenue model makes this sustainable and scalable for the future?		*what revenue model makes this sustainable and scalable for the future?
			*Do you have a critical path and contingency plan?
			*Do you have a team and budget? If not, how will you build a team and fund the development?
			*Do you have a roadmap, a stable process, development protocols, and documentation protocols to offer a clear path of development?
	*Is your pen mightier than the sword - ie, is thinking preceding action, or is the action not well-directed?		*Is your pen mightier than the sword - ie, is thinking preceding action, or is the action not well-directed?
	*Has this been proven in industry standards? If not, why not?		*Has this been proven in industry standards? If not, why not?

Marcin: /* Meta of Extreme Development - Approach Notes */

2016-01-13T14:38:45Z

Meta of Extreme Development - Approach Notes

← Older revision		Revision as of 14:38, 13 January 2016
Line 5:		Line 5:

	*Are you pursuing [[Test Driven Design]] of Extreme Manufacturing.		*Are you pursuing [[Test Driven Design]] of Extreme Manufacturing.
			*what revenue model makes this sustainable and scalable for the future?
	*Is your pen mightier than the sword - ie, is thinking preceding action, or is the action not well-directed?		*Is your pen mightier than the sword - ie, is thinking preceding action, or is the action not well-directed?
	*Has this been proven in industry standards? If not, why not?		*Has this been proven in industry standards? If not, why not?

Marcin: /* Meta of Extreme Development - Approach Notes */

2016-01-13T13:50:38Z

Meta of Extreme Development - Approach Notes

← Older revision		Revision as of 13:50, 13 January 2016
Line 19:		Line 19:
	*Do you have a clear statement of budget?		*Do you have a clear statement of budget?
	*Do you have a clear [[Critical Path]] defined?		*Do you have a clear [[Critical Path]] defined?
	*Are you designing your development process for a [[1000 Management Ratio]]?		*Are you striving for or designing your development process for a [[1000 Management Ratio]]?
	*

Marcin: /* Meta of Extreme Development - Approach Notes */

2016-01-13T13:48:25Z

Meta of Extreme Development - Approach Notes

Marcin at 13:45, 13 January 2016

2016-01-13T13:45:20Z

← Older revision		Revision as of 13:45, 13 January 2016
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) for the purpose of [[Distributive Enterprise]]. Until further distinctions are made, Extreme Enterprise is synonymous with Distributive Enterprise.

			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=		=Meta of Extreme Development - Approach Notes=

Line 11:		Line 13:
	*How is this leading to the fundamental solution of pressing world issues?		*How is this leading to the fundamental solution of pressing world issues?
	*What is the unique value proposition?		*What is the unique value proposition?
			*do you have a clear statement of goals?
			*do you have a clear statement of scope?
			*Do you have a clear statement of intended applications?
			*Do you have a clear statement of budget?
			*Do you have a clear [[Critical Path]] defined?

Marcin at 13:40, 13 January 2016

2016-01-13T13:40:12Z

← Older revision		Revision as of 13:40, 13 January 2016
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?

Marcin at 13:33, 13 January 2016

2016-01-13T13:33:18Z

← Older revision		Revision as of 13:33, 13 January 2016
Line 1:		Line 1:
	Extreme Development is the process of developing designs for [[Extreme Manufacturing]]. ~~There are several factors~~ to ~~this~~ 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.
	*Focus on [[Test Driven Design]]

			*Focus on [[Test Driven Design]] of Extreme Manufacturing.

← Older revision		Revision as of 13:48, 13 January 2016
Line 4:		Line 4:
	=Meta of Extreme Development - Approach Notes=		=Meta of Extreme Development - Approach Notes=

	*~~Focus on~~ [[Test Driven Design]] of Extreme Manufacturing.		*Are you pursuing [[Test Driven Design]] of Extreme Manufacturing.
			*Is your pen mightier than the sword - ie, is thinking preceding action, or is the action not well-directed?
	*Has this been proven in industry standards? If not, why not?		*Has this been proven in industry standards? If not, why not?
	*is this technology in common use? If not, why not?		*is this technology in common use? If not, why not?
Line 14:		Line 15:
	*What is the unique value proposition?		*What is the unique value proposition?
	*do you have a clear statement of goals?		*do you have a clear statement of goals?
	*do you have a clear statement of scope?		*do you have a clear statement of scope? I've, do you have a clear go and no-go list of things you are willing to engage in?
	*Do you have a clear statement of intended applications?		*Do you have a clear statement of intended applications?
	*Do you have a clear statement of budget?		*Do you have a clear statement of budget?
	*Do you have a clear [[Critical Path]] defined?		*Do you have a clear [[Critical Path]] defined?
			*Are you designing your development process for a [[1000 Management Ratio]]?
			*