Once you have a vision for your process change initiative, a consensus on the scope of work and vendor, and defined roles, you can start getting your hands dirty and really begin to roll out your BPM project. You can break the overall project up into the following stages:
1. Requirements gathering – This is where you pull together business requirements so that the development team can design a process. Pay careful attention to making sure you capture enough details. During this stage, you can ensure that the agreed scope of work for the first iteration meets expectations and is agreeable between all end users and stakeholders.
2. Envisioning – The envisioning stage involves a workshop focused on identifying and prioritizing strategic business objectives, related processes, and the metrics used to measure the identified processes. Using this information, it is possible to identify, quantify, and discuss the quick-win processes that will form the basis of your first BPM proof of concept (PoC).
3. Discovery – Once you identify good “candidate" processes, a discovery workshop ensures that you will be able to capture the business and functional requirements in a structured manner. This workshop helps you make sure that you consider all perspectives when compiling the business case.
4. Estimation – In the estimation stage, you approximate the work involved with each process. This is important for understanding the size of the project, as well as prioritizing processes according to their importance.
5. Construction and design – A process design is required for every piece of development. A design helps developers ensure they take into full account all business requirements in the new process model.
6. Designing workflows – Having gathered the business requirements, you can then define the process in detail for implementation stages. Getting this wrong will negatively impact project delivery and business user expectation.
7. Development – Your development team should work hand in hand with SMEs and BPM experts to understand the high-level business requirements and finer, technical details. Once some functionality has been developed, the team can then look to the end users for approval. With any feedback, the team can then adapt the design as needed to fit the users' needs and expectations.
8. Sprints – Progress with development is achieved in “sprints" – short, iterative rounds of work that help break down larger, complex projects. During each sprint, conduct daily meetings attended by all team members. At the end of each sprint, hold a retrospective meeting to review progress and make improvements for the next sprint.
9. Testing and deployment – With everything fully designed and developed, you are ready to see all of your effort put into action. But before you fully deploy the solution across your business, you will likely have to do some testing and fine-tuning.
Congratulations! You have made it through the first phase of your BPM initiative. Keep in mind that you should continue to monitor the processes from this first phase and use the feedback for continuous improvement. There will surely be other processes ripe for improvement through BPM in subsequent phases. Your journey is not over. It is only beginning.