Today I read an article titled "The Keys to BPM Project Success", written by Derek Miers and published in Jan 2006 issue of BPTrends. This article describes a recipe for execution of a successful BPM project. In this blog, I am trying to capture the steps of the proposed BPM Project Delivery Framework. The article provides quite a few examples while describing these steps, which are worth reading once to get convinced for significance of each of the given steps.
Step 1 – Establish the Steering Group consisting of executive head of the affected business area, CIO or lead IT executive, BPM program manager (or head of BPM CoE, if exists) and senior LOB managers from the functions directly affected. Conduct the initial Steering Group Workshop to obtain formal commitment from the business, linkage between BPM program & strategy of the organization and tactical agreement on the choice of project & consensus on scope.
Step 2: Identify the suitable target process which has relatively low level of maturity, high impact and low complexity. A good rule of thumb is to ensure that the selected initial project can complete within 3-6 months.
Step 3: Develop the business case that can be tied back to the Key Business Objectives (KBOs) of the organization. Techniques such as Goal Question Metric (GQM) technique developed by Victor Basili and his colleagues can be used to ensure alignment.
Step 4: Gain executive sponsorship
Step 5: Form the BPM Project Team consisting of BPM Project Manager, Senior User from the affected area, one or more SMEs from the LOB area, Lead Business Analysts and IT Specialists.
Step 6: Understand the process by using techniques such as Role Activity Diagrams (RADs) and Object State Transition Network (OSTN) techniques in addition to flow diagram based approaches.
Step 7: Identify breakthrough opportunities such as potential for faster cycle times, enhanced customer service, channel integration, minimizing the number of times of handling the work items,role rationalization, management and monitoring of personnel performance and better exception management.
Step 8: Develop and prototype on the BPM suite
Step 9: Implement and align organizational change
Besides this recipe for sucess, the article also provides a 16-points list of pitfalls to avoid. In all, the article is a good read of anyone interested and/or involved in initial BPM projects in an organization.