The deployment of Business Process Management (BPM) projects is particularly susceptible to ballooning costs, and delayed implementation, particularly if the Business has not established its priorities at the outset and so tries to jam all its requirements into the first modeling exercise.
There are a number of actions that you can take to maintain control of your BPM project and for ensuring that you do not get hit with unforeseen, hidden costs.
Click here to download
You have decided to consider deploying Business Process Management (BPM) to solve a compelling issue in a business function, or are evaluating how BPM can deliver an agile platform to leverage your investment in a Services Oriented Architecture, but are faced with a bewildering choice of tools and approaches. The BPM market is maturing and consolidating and it’s difficult to select a supplier. The choice ranges from 600 Pound Gorillas like Oracle, IBM and SAP; pure play vendors like K2.net, Global 360, Pegasystems, Appian, Savvion and Lombardi; Middleware vendors such as Sun, Software AG, Tibco; and BI vendors looking to diversify. We look at some approaches to software selection that may help.
Click here to download
Business Process Management (BPM) projects should create a mutual dependency between IT and the Business that requires an unprecedented amount of team work and process definition. In best practise BPM projects, at least 60% of the effort should involve change management and getting organisations to think about process in the business. But if the Business and IT are not working together at the outset, there will be no culture change and problems will occur. This paper details some useful steps that can be taken to ensure the success of your BPM project.
Click here to download