Week 6 of 8
SIT, UAT and roles
Infor’s guide describes the Test phase simply: all workstreams synchronize for end-to-end SIT against agreed entry and exit criteria, then UAT confirms the business accepts the solution. The hard part is making both produce evidence a sponsor can sign.
Security has two layers. Infor OS roles decide who reaches the portal and applications; application security, such as M3 roles or CloudSuite Industrial groups and IDO permissions, decides what they can do. Test both. And plan for sign-off delays: in Panorama’s 2026 report, almost a quarter of projects ran over schedule, most often for organizational reasons.
This week: make SIT end-to-end and UAT signable
- Write SIT scenarios as chains, e.g. EDI order → credit check → MRP → manufacturing order → operation reporting → receipt → shipment → invoice → payment.
- Every expected result must be checkable: an order number, a status, a posted amount, a OneView reference. Never "screen appears".
- Run UAT with production roles, one test user per tester, and include negative tests: what each role must not be able to do.
- Agree the UAT sign-off route now: process owner, functional lead, test manager, program director.
Number of the week
Almost 1 in 4
ERP projects ran over schedule; organizational issues such as delayed sign-offs were the most common cause.
Source: Panorama Consulting, The 2026 ERP ReportUse this week
- SIT Cycle Plan & Entry/Exit Criteria →
Cycles, scenarios, entry and exit criteria and a daily burn-down.
- UAT Sign-Off Form (Word) →
Results, accepted defects, controls tested and signatures per process owner.
- Defect Severity & Triage Matrix →
One severity language for SIT, UAT and hypercare.
Next week: cutover, go/no-go and hypercare. What the room needs to see.
Get the playbook in your inbox, one week at a time
Subscribe free and every template in the library is yours.