Quality Control is concerned with the accuracy of the result. Scope Verification is concerned with the acceptance of the results.
Sounds confusing, doesn’t it? At this point- when the project deliverables are sitting in front of you, with the bulk of the project behind you, it wouldn’t be. Variable depending on how stringent you were with your discovering, planning and controlling and execution, you will probably have a load of things to look through to make sure your QC and SV is sharp.
Scope Verification
SOW is the high level, easiest reference point. It’s what the client will be looking at to verify scope as well. From there, don’t forget the major outputs of the SOW- Scope management plan, WBS including work packages, etc… to ensure all components are covered.
Was there a change request? Of course there was! Did you update the scope baseline (BRD, TRD, etc..?) to reflect it? Maybe you did, maybe you didn’t. As long as your articulated the changes in a CR, you’re probably covered, but let this be a lesson to you. Now go sit in the corner and think about what you’ve done.
Quality Control
This is outside the box of normal QCM, which I would highly recommend you familiarize yourself with if you’re not already living and breathing your commitment to meeting and exceeding client expectations (and no- that’s not an invitation to gold plating). What’s the goal of QC? Basically acceptance of the work your team produced. Who is ultimately accountable if the client encounters a bug? If your answer is the resource, go sit in the corner again.
I’ve had clients encounter errors in UAT, and it’s embarrassing. They’re not happy. You’re not happy. You’re in a scramble to save face and fix it. On the plus side, they’re excellent learning lessons, because in the next delivery, you’re making sure you inspect the work packages like no one else- and maybe it takes a little more time, or maybe you’re hustling to get it done before UAT, but over time, I’ve learned not only to put in enough time in the schedule for enough rounds of QA to fix everything, but also how to look for issues before formalized QA starts, (which of course, is part of Plan Quality, a factor of QCM.
In the end, scope and quality are related, but not like a brother and sister, more like second cousins that get together twice a year for a beer and argue about Hockey and Politics (I have a second cousin like that).