Gauging Maturity of your BPM Strategy - part 2 / 2
- by Sanjeev Sharma
In my earlier post I had discussed the essence of maturity assessment and the business imperative for doing the same in the context of BPM. In this post I will discuss Oracle’s BPM Maturity assessment methodology.
Oracle’s BPM Maturity model comprises of the following components:
Maturity – represents stages of evolution of your BPM capability with 0 being the lowest level and 5 being the highest level
Domain – represents multiple perspectives both technical and business oriented against which your BPM capability can be assessed
Adoption – represents scale of BPM rollout starting at the project level to the enterprise level
Note: Your BPM capability can be at different levels of maturity for the different domains.
Oracle’s BPM assessment methodology measures the maturity of your BPM capability at the individual domain level as well as the aggregate level. The output of Oracle’s BPM assessment benefits you in two ways:
Gap Analysis by comparing the “As-Is” BPM capability with the desired “To-Be” BPM capability along the various domains (see Figure 1)
Systematic Adoption by aligning evolution of BPM capability with its rollout in multiple phases (see Figure 2)
