Charter for the BPM engine: Difference between revisions
wikademia>Chungw m changed section capitalization |
wikademia>Chungw m corrected links to properly named learning pages |
||
| Line 28: | Line 28: | ||
This Charter does not impose a rigid structure upon an organization. Rather, suggestions are made regarding fundamental responsibilities. Specific titles and roles can and should be modified. Individuals may find themselves filling multiple roles at various times in a program's lifetime. | This Charter does not impose a rigid structure upon an organization. Rather, suggestions are made regarding fundamental responsibilities. Specific titles and roles can and should be modified. Individuals may find themselves filling multiple roles at various times in a program's lifetime. | ||
Defining a staged timeline is covered in the [[Charter for BPM Investment]] because it is intimately tied to an organization's budget and appetite for implementation. | Defining a staged timeline is covered in the [[Charter for bpm investment|Charter for BPM Investment]] because it is intimately tied to an organization's budget and appetite for implementation. | ||
Also, while the engine includes all people supporting the portfolio, end-users are covered in the [[Charter for BPM Democracy]]. This Charter focuses on program teams that are governing, delivering, and supporting the solutions. | Also, while the engine includes all people supporting the portfolio, end-users are covered in the [[Charter for bpm democracy|Charter for BPM Democracy]]. This Charter focuses on program teams that are governing, delivering, and supporting the solutions. | ||
| Line 224: | Line 224: | ||
*<u>Methods</u> - Common methods allow projects to provide similar metrics about their delivery capabilities, business benefits, and operational costs. This common bookkeeping allows the Leadership tier to better manage the program for success, continuing with beneficial projects and tweaking or terminating others. | *<u>Methods</u> - Common methods allow projects to provide similar metrics about their delivery capabilities, business benefits, and operational costs. This common bookkeeping allows the Leadership tier to better manage the program for success, continuing with beneficial projects and tweaking or terminating others. | ||
The [[Charter for BPM Investment]] separates the maturity curve into three stages. The middle stage of ''Adopt'' is where most of these transitions are observed, with ''Validate'' and ''Transform'' representing the before and after, respectively. | The [[Charter for bpm investment|Charter for BPM Investment]] separates the maturity curve into three stages. The middle stage of ''Adopt'' is where most of these transitions are observed, with ''Validate'' and ''Transform'' representing the before and after, respectively. | ||
=== Implementation === | === Implementation === | ||
An organization must define a timeline and roadmap for realizing the engine. Here are some preliminary steps, with further discussion provided in the [[Charter for BPM Investment]]. | An organization must define a timeline and roadmap for realizing the engine. Here are some preliminary steps, with further discussion provided in the [[Charter for bpm investment|Charter for BPM Investment]]. | ||
#<u>Specify Requirements</u> - For each stage, specify the requirements for the engine. The immediately imminent stages will be more detailed than future stages. Clear and concise quality requirements for the roadmap are essential for driving the change management and adoption aspects of the program. | #<u>Specify Requirements</u> - For each stage, specify the requirements for the engine. The immediately imminent stages will be more detailed than future stages. Clear and concise quality requirements for the roadmap are essential for driving the change management and adoption aspects of the program. | ||
#<u>Establish a Roadmap</u> - Take those requirements, and map them to a timetable. Communicate on the achievement of intermediate goals. | #<u>Establish a Roadmap</u> - Take those requirements, and map them to a timetable. Communicate on the achievement of intermediate goals. | ||
#<u>Regularly Revisit</u> - Aggregate results and new information to drive revisions to the requirements and roadmap. Recalling [[The | #<u>Regularly Revisit</u> - Aggregate results and new information to drive revisions to the requirements and roadmap. Recalling [[The charters for bpm program governance - an overview#Tenets|Tenets 1 and 2]], it is okay to make mistakes as long as mechanisms are in place to detect, to correct, and to avoid in the future. | ||
| Line 238: | Line 238: | ||
*As a program evolves, the mixture of people will change. Early stage programs will focus more on execution and confirming program viability. Over time, the people will specialize more. A smaller program requires more versatile resources to cover the range of responsibilities. As a larger set of projects imposes greater demand upon the engine, there will be more people filling the various roles. This is expected, but be prepared to equip each resource with adequate skills. | *As a program evolves, the mixture of people will change. Early stage programs will focus more on execution and confirming program viability. Over time, the people will specialize more. A smaller program requires more versatile resources to cover the range of responsibilities. As a larger set of projects imposes greater demand upon the engine, there will be more people filling the various roles. This is expected, but be prepared to equip each resource with adequate skills. | ||
*Tools will change over time. There is a limited lifetime for infrastructure, and software products change in their capabilities. Plan for the tools to change on a regular cadence, allowing new possibilities to be incorporated into the delivery of projects. | *Tools will change over time. There is a limited lifetime for infrastructure, and software products change in their capabilities. Plan for the tools to change on a regular cadence, allowing new possibilities to be incorporated into the delivery of projects. | ||
*Use the successes and deficiencies of projects to adjust the program. Do not stick to the roadmap simply because it was established at the outset. Remember [[The | *Use the successes and deficiencies of projects to adjust the program. Do not stick to the roadmap simply because it was established at the outset. Remember [[The charters for bpm program governance - an overview#Tenet_1|Tenet 1]]. | ||