BPM Implementation Best Practices – Part IV

BPM Implementation Best Practices – Part IV

Methodology adopted for BPM programs/projects plays very important role in outcome.

There are several well defined methodologies for managing and executing BPM programs. However most of them remain as marketing tools and restrict themselves to a bunch of slides or whitepapers. Unless, there is disciplined approach in execution, methodologies are never followed. This in turn causes unpredictable outcome, higher maintenance cost, long deployment/change cycles and lack of collaboration between business and IT.

For a longer term success, predictable outcome, and accountability of all stakeholders; it is imperative to ensure that the most appropriate methodology is followed. Every BPM vendor or implementation company claims to have some methodology. While such methodology can be a very useful starting point, a BPM program manager must make sure to tune that up to suit the culture and practices of the organization. Once again, first pilot project becomes even more important from this perspective.

Methodology adopted for program/project execution must ensure:

  • Process model is made explicit upfront and approach that fosters collaboration between Process Owner and IT.
  • For human tasks, wire-frames are build and signed-off by business users upfront. Wire-frames must be built using native form designers supported by BPMS (unless it is absolutely imperative to use other tools).
  • Use and creation of re-usable components to reduce maintenance cost and consistency of interfaces and integration approaches across multiple solutions.
  • Periodic end-user demonstrations during development phase and ability to incorporate feedback.

Above points are of course in addition to best practices that should be followed and are being discussed in this series of blog.

Leave a Reply

Your email address will not be published. Required fields are marked *