Last week, I talked about managing expectations surrounding your vision for a solution.
Looking at a BPM project using the ADCI model [derived from the ‘big’ consulting companies], the 4 phases are Analysis, Design, Construction and Implementation.
The analysis step is critical. If this is done properly, then the rest is ‘fairly’ easy. It all starts with your ‘vision’ of how you would like your business to function. Working with your consultant/vendor, you will make compromises where it makes sense. Either the feature is too expensive or doesn’t exist. The resulting ‘vision’ that is doable will dictate your expectations. At this point all of your expectations should be doable – success is achievable.
I do like to point out early and often that it is a bad idea to change the requirements.
1) It is impossible for a programmer to program to a moving target.
2) Changes quickly add $ dollars to your project.
3) The longer a project takes, the greater the chance of something going wrong.
4) The more time a project takes, the more enthusiasm wanes.
Obviously, the odds of getting it absolutely right the first time is slim.
Just do it. Get the solution out there while there is some enthusiasm. Get people using it. Gather their suggestions of how to make it better. Their suggestions will likely change what you thought should be altered. Create new requirements for ‘Phase 2’ and go from there.
‘Phase 2’ becomes a new project. It starts with a new enthusiasm and internal sales pitch. If this project takes longer, it is OK because your company has seen ‘success’ and their expectations include knowing that the ‘Phase 2’ project isn’t just a pipe dream – it will get done.
Your BPM project, managed properly, can bring your company some significant financial benefits. Now is a good time to get started.
What has been your experience?