Charter for the BPM engine: Difference between revisions
wikademia>Chungw m changed section capitalization |
wikademia>Eme |
||
| (12 intermediate revisions by 2 users not shown) | |||
| 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 50: | Line 50: | ||
| bgcolor="gray" | <center><font color="white">'''Representative Groups'''</font></center> | | bgcolor="gray" | <center><font color="white">'''Representative Groups'''</font></center> | ||
|- | |- | ||
| | | '''1: Leadership''' | ||
Sets the direction and empowers resources | Sets the direction and empowers resources | ||
| | | valign="top" | | ||
*Determine, communicate, and validate program objectives | *Determine, communicate, and validate program objectives | ||
*Provide funding and resources | *Provide funding and resources | ||
*Establish a supportive environment, including arranging contributions from related, non-BPM programs | *Establish a supportive environment, including arranging contributions from related, non-BPM programs | ||
*Resolve conflicts | *Resolve conflicts | ||
| | | valign="top" | | ||
*Executive | *Executive | ||
*Finance | *Finance | ||
| Line 63: | Line 63: | ||
*Delivery | *Delivery | ||
|- | |- | ||
| | | '''2: Execution''' | ||
Implements the program and provides results | Implements the program and provides results | ||
| | | valign="top" | | ||
*Select, deliver, and validate projects | *Select, deliver, and validate projects | ||
*Recruit and retain people | *Recruit and retain people | ||
| Line 71: | Line 71: | ||
*Define and incorporate methods | *Define and incorporate methods | ||
*Escalate conflicts | *Escalate conflicts | ||
| | | valign="top" | | ||
*Business Owners | *Business Owners | ||
*Senior Management | *Senior Management | ||
| Line 85: | Line 85: | ||
| bgcolor="gray" | <center><font color="white">'''Responsibilities'''</font></center> | | bgcolor="gray" | <center><font color="white">'''Responsibilities'''</font></center> | ||
|- | |- | ||
| | | ''Executive Sponsor'' | ||
| | | valign="top" | | ||
*Sets direction and strategic objectives | *Sets direction and strategic objectives | ||
*Ultimate decision maker for conflicts | *Ultimate decision maker for conflicts | ||
|- | |- | ||
| | | ''Financial Director'' | ||
| | | valign="top" | | ||
*Sets funding plan for accomplishing objectives | *Sets funding plan for accomplishing objectives | ||
*Standardizes the critical success requirements (metrics) for projects | *Standardizes the critical success requirements (metrics) for projects | ||
*Validates alignment with defined targets | *Validates alignment with defined targets | ||
|- | |- | ||
| | | ''Chief Technologist'' | ||
| | | valign="top" | | ||
*Defines the technical landscape of software and systems | *Defines the technical landscape of software and systems | ||
*Incorporates new technologies | *Incorporates new technologies | ||
*Standardizes designs and patterns for reuse | *Standardizes designs and patterns for reuse | ||
|- | |- | ||
| | | ''Portfolio Director'' | ||
| | | valign="top" | | ||
*Ensures prioritized selection and successful delivery of BPM solutions | *Ensures prioritized selection and successful delivery of BPM solutions | ||
*Manages the talent required for the portfolio | *Manages the talent required for the portfolio | ||
| Line 116: | Line 116: | ||
| bgcolor="gray" | <center><font color="white">'''Responsibilities'''</font></center> | | bgcolor="gray" | <center><font color="white">'''Responsibilities'''</font></center> | ||
|- | |- | ||
| | | ''Business Owners'' | ||
| | | valign="top" | | ||
*Ensure alignment between solutions and objectives | *Ensure alignment between solutions and objectives | ||
*Enforce the change management policies, including minimum quality criteria | *Enforce the change management policies, including minimum quality criteria | ||
|- | |- | ||
| | | ''Senior Management'' | ||
| | | valign="top" | | ||
*Coordinate functional areas to deliver results | *Coordinate functional areas to deliver results | ||
|- | |- | ||
| | | ''Technical Staff'' | ||
| | | valign="top" | | ||
*Design and implement requisite technologies for solutions | *Design and implement requisite technologies for solutions | ||
*Design and implement scalable platform infrastructure | *Design and implement scalable platform infrastructure | ||
| Line 132: | Line 132: | ||
*Support deployed solutions | *Support deployed solutions | ||
|- | |- | ||
| | | ''Program Management'' | ||
| | | valign="top" | | ||
*Deliver solutions to specified targets | *Deliver solutions to specified targets | ||
*Build roadmaps for solution opportunities that might be delivered in later increments | *Build roadmaps for solution opportunities that might be delivered in later increments | ||
| Line 147: | Line 147: | ||
*Coaching - Assisting in issue avoidance and risk management. | *Coaching - Assisting in issue avoidance and risk management. | ||
Here is a suggested structure for the tiers | Here is a suggested structure for the tiers. As mentioned earlier, individuals might need to participate within multiple roles and responsibilities, especially during the early stages of a program. | ||
[[Image: | [[Image:BPM_Governance_Structure.png|thumb|none|Simplified governance organization.]] | ||
| Line 160: | Line 160: | ||
| bgcolor="gray" | <center><font color="white">'''Requirements'''</font></center> | | bgcolor="gray" | <center><font color="white">'''Requirements'''</font></center> | ||
|- | |- | ||
| | | ''Demand Management'' | ||
| Support prioritization of opportunities based on their impact against the strategic objectives of the business. This means picking meaningful projects that provide benefit. | | Support prioritization of opportunities based on their impact against the strategic objectives of the business. This means picking meaningful projects that provide benefit. | ||
|- | |- | ||
| | | ''Supply Management'' | ||
| Provide sufficient engine capacity to deliver the selected opportunities. This includes having a ramp-up plan for skilled resources and infrastructure, whether they be centrally or departmentally allocated. These resources can also be sourced externally. | | valign="top" | Provide sufficient engine capacity to deliver the selected opportunities. This includes having a ramp-up plan for skilled resources and infrastructure, whether they be centrally or departmentally allocated. These resources can also be sourced externally. | ||
|- | |- | ||
| | | ''Innovation'' | ||
| Parts of the organization must be able to advance the state-of-the-art, either in their approach or in their tooling. Innovation provides an opportunity for validating options with limited investment. | | valign="top" | Parts of the organization must be able to advance the state-of-the-art, either in their approach or in their tooling. Innovation provides an opportunity for validating options with limited investment. | ||
|- | |- | ||
| | | ''Delivery Agility'' | ||
| Provide a mechanism for projects to adjust their course to changing objectives. This includes the ability to terminate a project early if it is not able to deliver sufficient benefit to justify the investment. | | valign="top" | Provide a mechanism for projects to adjust their course to changing objectives. This includes the ability to terminate a project early if it is not able to deliver sufficient benefit to justify the investment. | ||
|- | |- | ||
| | | ''Change Management'' | ||
| Allow the pace of deployment to be adjusted for an organization's culture. A balance should be determined by certain factors, including | | valign="top" | Allow the pace of deployment to be adjusted for an organization's culture. A balance should be determined by certain factors, including | ||
*Significance of changes, | *Significance of changes, | ||
*Quality of the releases, | *Quality of the releases, | ||
| Line 179: | Line 179: | ||
*Capacity to incorporate feedback into roadmap. | *Capacity to incorporate feedback into roadmap. | ||
|- | |- | ||
| | | ''Continuous Improvement'' | ||
| Allow for incremental delivery of benefit over identified time windows. It must be possible to divide feature sets into groups and to have those groups delivered in staged releases. | | valign="top" | Allow for incremental delivery of benefit over identified time windows. It must be possible to divide feature sets into groups and to have those groups delivered in staged releases. | ||
|} | |} | ||
</center> | </center> | ||
| Line 193: | Line 193: | ||
| bgcolor="gray" | <center><font color="white">'''Requirement'''</font></center> | | bgcolor="gray" | <center><font color="white">'''Requirement'''</font></center> | ||
|- | |- | ||
| | | ''Applicability'' | ||
| | | valign="top" | | ||
*Provides features that allow the methods to be employed. | *Provides features that allow the methods to be employed. | ||
*Matches the skillsets and capabilities of the people involved - at all levels. | *Matches the skillsets and capabilities of the people involved - at all levels. | ||
*Meets today's requirements and also allows for growth. | *Meets today's requirements and also allows for growth. | ||
|- | |- | ||
| | | ''Technical Fit'' | ||
| | | valign="top" | | ||
*Fits with the IT strategy - matches standards and protocols used by the organization. | *Fits with the IT strategy - matches standards and protocols used by the organization. | ||
|- | |- | ||
| | | ''Comprehensiveness'' | ||
| | | valign="top" | | ||
*Facilitates the realization of objective goal setting with project-level benefits achievement. | *Facilitates the realization of objective goal setting with project-level benefits achievement. | ||
*Provides measurement and analysis capabilities to enable validation. | *Provides measurement and analysis capabilities to enable validation. | ||
| 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]]. | ||
| Line 245: | Line 245: | ||
=== Behaviors === | === Behaviors === | ||
*[[An engine structured for success]] | *[[An engine structured for success|An Engine Structured For Success]] | ||
*[[Method of innovation - incubators]] | *[[Method of innovation - incubators|Method of Innovation - Incubators]] | ||
*[[Sharing - infrastructure cost models]] | *[[Sharing - infrastructure cost models|Sharing - Infrastructure Cost Models]] | ||
*[[Tools - plan for adapting]] | *[[Tools - plan for adapting|Tools - Plan For Adapting]] | ||
=== Anti-Behaviors === | === Anti-Behaviors === | ||
*[[Insufficient execution methods - six sigma falls short]] | *[[Insufficient execution methods - six sigma falls short|Insufficient Execution Methods - Six Sigma Falls Short]] | ||
| Line 263: | Line 263: | ||
The more that skilled resources can be shared, that common tools leveraged, and that the methodology adapted based on experience, then the more quickly those goals can be realized. Comparatively, solutions that otherwise deliver the same business return will have a higher return on investment if they share the engine than if they do not. | The more that skilled resources can be shared, that common tools leveraged, and that the methodology adapted based on experience, then the more quickly those goals can be realized. Comparatively, solutions that otherwise deliver the same business return will have a higher return on investment if they share the engine than if they do not. | ||
== Lesson exercises == | |||
[[Category:Charters for business process management program governance]] | |||
== Related lessons == | |||
{{ntnes}} | |||
{| | |||
| | |||
| [[The charters for bpm program governance - an overview|The Charters for BPM Program Governance - An Overview]] | |||
|- | |||
| | |||
| [[Charter for the bpm engine|Charter for the BPM Engine]] | |||
|- | |||
| | |||
| [[Charter for bpm democracy|Charter for BPM Democracy]] | |||
|- | |||
| | |||
| [[Charter for alignment|Charter for Alignment]] | |||
|- | |||
| | |||
| [[Charter for conflict resolution|Charter for Conflict Resolution]] | |||
|- | |||
| | |||
| [[Charter for bpm investment|Charter for BPM Investment]] | |||
|- | |||
| | |||
| [[A charters glossary|A Charters Glossary]] | |||
|} | |||