Archive:Tools - plan for adapting - Revision history

wikademia>Wikademia: moved Tools - plan for adapting to Archive:Tools - plan for adapting

2009-04-11T18:17:38Z

moved Tools - plan for adapting to Archive:Tools - plan for adapting

← Older revision	Revision as of 18:17, 11 April 2009
(No difference)

wikademia>Wikademia at 18:02, 11 April 2009

2009-04-11T18:02:05Z

← Older revision		Revision as of 18:02, 11 April 2009
Line 5:		Line 5:

	They accepted that the first projects would struggle with some of the changes in technology. They took that hit early with plans to invest in additional capabilities for their people at a later stage of the program. While the early engine did not completely meet the applicability requirements outlined for tools in this Charter, a decision was made to leverage external resources in the short-term to more quickly realize the benefits of BPM.		They accepted that the first projects would struggle with some of the changes in technology. They took that hit early with plans to invest in additional capabilities for their people at a later stage of the program. While the early engine did not completely meet the applicability requirements outlined for tools in this Charter, a decision was made to leverage external resources in the short-term to more quickly realize the benefits of BPM.


	== Applies to ==		== Applies to ==
Line 12:		Line 11:
	\| [[Charter for the bpm engine\|Charter for the BPM Engine]]		\| [[Charter for the bpm engine\|Charter for the BPM Engine]]
	\|}		\|}


	[[Category:(Anti-)Behaviors of business process management program governance]]		[[Category:(Anti-)Behaviors of business process management program governance]]
			{{ntnes}}

wikademia>Wikademia: 3 revisions

2009-04-11T05:54:27Z

3 revisions

← Older revision	Revision as of 05:54, 11 April 2009
(No difference)

wikademia>Chungw: added category

2009-04-10T21:46:58Z

added category

← Older revision		Revision as of 21:46, 10 April 2009
Line 12:		Line 12:
	\| [[Charter for the bpm engine\|Charter for the BPM Engine]]		\| [[Charter for the bpm engine\|Charter for the BPM Engine]]
	\|}		\|}


			[[Category:(Anti-)Behaviors of business process management program governance]]

wikademia>Chungw: added navigation to parent charter

2009-04-10T19:01:31Z

added navigation to parent charter

← Older revision		Revision as of 19:01, 10 April 2009
Line 5:		Line 5:

	They accepted that the first projects would struggle with some of the changes in technology. They took that hit early with plans to invest in additional capabilities for their people at a later stage of the program. While the early engine did not completely meet the applicability requirements outlined for tools in this Charter, a decision was made to leverage external resources in the short-term to more quickly realize the benefits of BPM.		They accepted that the first projects would struggle with some of the changes in technology. They took that hit early with plans to invest in additional capabilities for their people at a later stage of the program. While the early engine did not completely meet the applicability requirements outlined for tools in this Charter, a decision was made to leverage external resources in the short-term to more quickly realize the benefits of BPM.


			== Applies to ==
			{\|
			\| [[Image:Engine.gif\|left\|link=Charter for the bpm engine]]
			\| [[Charter for the bpm engine\|Charter for the BPM Engine]]
			\|}

wikademia>Chungw: Initial behavior page

2009-04-09T20:09:14Z

Initial behavior page

New page

== Summary ==
The specific requirements for the engine and the ability to satisfy those requirements will vary over the program's lifetime. It is unrealistic to assume that a plan for the engine can be constructed years into the future since things are constantly changing. It is also likely that even if such a plan could be produced it would be impossible to fulfill all of the requirements right away. In building the engine today, recognize where short-term tradeoffs are acceptable to get the program in motion.

Consider an organization that was steeped in mainframe technologies and that went down the route of non-Java systems prior to the beginning of their BPM journey. Despite a lack of in-house competence with application servers or webservices, they opted for Java-based BPM software.

They accepted that the first projects would struggle with some of the changes in technology. They took that hit early with plans to invest in additional capabilities for their people at a later stage of the program. While the early engine did not completely meet the applicability requirements outlined for tools in this Charter, a decision was made to leverage external resources in the short-term to more quickly realize the benefits of BPM.