Ten years ago we wrote about the importance of Project Assurance, and how it was a methodology for keeping your Supply Management Project on Track (Part I, Part II, Part III, Part IV, and Part V).
We told you that Project Assurance, which takes a proactive approach and tries to identify issues, and implement mitigations, before they arise, involves the organization periodically stopping to objectively assess project failure points as they arise, typically with the help of an outside third party who can be completely objective, to identify what is and is not being done well and what could cause failure later if not adequately addressed now.
In traditional Project Assurance, there are six health assessments at six critical points in every project (for each of the six initial project phases defined by the classic waterfall project methodology). In particular, there is an assessment at each of the following steps:
- Strategy (Pre-Presentation)
- Acquisition (Pre-Vendor Selection)
- Planning (Pre-Design)
- Design (Pre-Acceptance)
- Development (Pre-Testing)
- Testing & Training (Pre-Acceptance)
And that the right assurance expert can help you with
- expectation management during the strategy development
- narrowing the procurement gap during the acquisition phase
- aligning the troops during the planning phase
- delineate the disconnect during the design phase
- evaluate for acceptance during the development phase
- tame the transition during the testing and training phase
And we stand by these posts and the importance of a third party expert helping you with the assurance ten years later, because we feel that if more companies adopted the methodology, we might not be in the situation a decade late where we still have a ridiculously high failure rate in procurement technology projects (as well as technology projects as a whole), that, depending on the study quoted, still exceeds 80% in some cases.
But we also recognize that, given the complexity of both modern Procurement (which hasn’t had so many issues to deal with simultaneously in over two decades), and modern technology, project assurance isn’t enough to save a project that isn’t planned right from the get go. (You just don’t have time to identify and fix all the problems once things get underway and you have the army of grunts simultaneously doing the implementation, all the integrations, and training as they try to rush an enterprise project that used to take two years and get it done in 9 months so they can promise payback within a year (which never happens when they do this — but that would be a different rant).
So, in this short series, we are going to dive into the project steps and help you understand what you need to do to get it as right as you can and greatly increase your odds of success.