Legislating Competency: Another Perspective
- July 14, 2015
- 0 Comments
Anatoly Belaychuk wrote a post in response to one of mine on the topic of legislating competency. We often find ourselves agreeing on topics related to BPM, despite very different backgrounds and experiences with different BPM tools. I take some comfort from the fact that people with such disparate experiences still find the common ground of BPM and BPMN best practices to be fertile ground for conversation and discussion.
Key points from Anatoly’s piece:
- “Experienced BPM team typically needs about 5 iterations to develop a viable process model and usable process application. If either customer or provider is unexperience, double this figure. The initial and resulting views of the process differ like night and day” – interestingly, most of our sizable projects are 4-6 iterations from start to first production deployment.
- “It’s well known that “unhappy customer produces unhappy developer.” Yet the reverse is also true: cut the contract to the point where provider aren’t much interested on the financial terms and they will think more about cutting their costs than about product quality and ultimate business result for the customer.” – exactly the issue. If the deal you’re asking of the vendor is too good to be true, be careful: they may give it to you by cutting all the quality and cost out of it, including “success” as the most costly element to delivery for any project.