Long before the post-implementation audit (PIA) begins, write up a clear business case that delineates and breaks down the cost of the project, the soft and hard benefits, the expected ROI, and when the ROI will be fully achieved.
Keep scrupulous records of all the changes that are made to the system and to the project plan during the implementation. A Web-based version control or collaboration tool can make this easier.
Identify the members of the audit team.
Schedule a kick-off PIA meeting to identify all the logistics that need to take place to perform the audit.
Review the business case, the initial scope of work and all the change orders. Around the same time, schedule interviews with users or send out satisfaction surveys. Also survey implementation team members to find out how well they think the various project objectives were met. Test the system and its controls. Examine the quality of the data. Take a sample of the transactions to make sure they’re being processed the way they should. Engage the finance department to conduct its review of the system’s payoff.
Compare audit findings with the business case to see if you hit your target.
Gather lessons learned. Identify what went well, what didn’t and why. Determine how you can address what didn’t go well in future implementations.
Perform follow-up reviews, if necessary.