Most ERP programmes do not fail because nobody tested. They fail because at the end of UAT nobody can say, with a number, whether the business is ready to go live.
This toolkit is the control set for that question. Eleven linked worksheets take user acceptance testing from scope through scripts, execution, defects and sign-off, and end in a calculated GO / NO-GO verdict that reads every other sheet.
It is deliberately ERP-agnostic. The control questions do not change with the vendor, so it works the same whether the target is SAP, Oracle, Dynamics 365, NetSuite, Infor or a banking core.
WHAT IS INSIDE
01 Test Scope: business processes in scope, criticality and owners. The single source of truth every other sheet looks up.
02 Test Scripts: one row per test case, with preconditions, steps, data, expected and actual result. A Process ID that does not exist in sheet 01 is flagged in red.
03 Coverage Matrix: calculated. Planned versus executed versus passed per process, with a GAP verdict when a critical process is not fully passed.
04 Cycle Plan: SIT, UAT 1, UAT 2 and regression, with dates, environment and calculated counts per cycle.
05 Defect Log: severity, root cause, retest result and days open, with Script IDs validated against sheet 02.
06 Entry and Exit Criteria: the gate for each cycle. Write the threshold before the cycle starts; Met is calculated against it.
07 Sign-off Tracker: calculated readiness per process, meaning every script passed and no open critical or major defect. A person still signs.
08 Decision Log: test scope and approach decisions, with the cost of reversing each one.
09 RACI: who executes, who accepts, who to call when a cycle is blocked.
10 Dashboard: calculated roll-up across every sheet, ending in GO / NO-GO.
Lists: every dropdown value, editable.
BUILT IN
A calculated GO / NO-GO verdict. It reads NO-GO while a critical process is not fully passed, a critical defect is open, or an entry or exit criterion is unmet.
Cross-sheet validation: a Process ID or Script ID that does not exist upstream is flagged, not silently accepted.
Readiness per process calculated from the evidence, not from an opinion.
Dropdowns throughout, so a test team of twelve fills it in the same way. A worked example on the first row of every sheet shows the level of detail expected.
No macros. It opens in Excel, LibreOffice and Google Sheets, and every sheet is set up to print at page width.
WHO IT IS FOR
ERP implementation consultants and test managers, UAT leads, process owners who have to sign off before go-live, and internal teams preparing a first go-live.
WHERE IT DOES NOT FIT
If your programme already runs test management in Jira with Xray, qTest or ALM, you do not need this workbook.
LICENCE
Use and adapt this workbook on your own organisation's implementation, replacement or consolidation projects, and on client engagements delivered for third parties, by the individual or firm that purchased it. Do not resell, redistribute or publish it, in whole or in part, as a template or as part of another product. One purchase covers one user.
Got a question about the product? Email us at support@flevy.com or ask the author directly by using the "Ask the Author a Question" form. If you cannot view the preview above this document description, go here to view the large preview instead.
Source: Best Practices in IT Testing, ERP Excel: ERP UAT, Test Management, and Go-Live Readiness Toolkit Excel (XLSX) Spreadsheet, Cutover Kit