SaatPro
Where Technology Meets Clarity
Section 1: The “Judge and Jury” – User Acceptance Testing (UAT)
It was exactly two weeks before the official Canada launch date. The code was “Feature Complete,” the final performance tests were passing, and the Delhi ODC felt a cautious sense of relief. But the most dangerous hurdle remained: UAT (User Acceptance Testing). This wasn’t a technical test by 7Pro; it was a functional test by the actual Canadian bank clerks and potential QT Money customers.
Mohd Tariq was monitoring the Jira bug tracker, and the “Issue Type: UAT-Observation” column was growing fast. “Kapil,” Tariq said, a familiar tension in his voice. “The UAT testers in Toronto just logged 14 ‘UI Papercuts’ in the last hour. They say the biometric scan animation is ‘too slow’ and the font size on the digital receipt is ‘unreadable’ on older iPhones.”
“Are these deviations from the original spec?” Kapil Mehta asked, opening the Traceability Matrix on his screen.
“Technically, no,” Tariq admitted. “The spec didn’t define animation speed. But if the users don’t ‘Accept’ the product, we don’t get the Final Sign-off. And without sign-off, there is no final payment.”
Kapil knew this was the Validation Scope process in action. The product could be technically perfect (Quality Control), but if it didn’t meet the user’s definition of “Fitness for Use,” it would fail the project.
Section 1 Breakdown: The PMP & ITIL Lens
- User Acceptance Testing (UAT): The final stage of the software testing process where actual users test the software to see if it can handle required tasks in real-world scenarios. It answers the question: “Did we build the right thing for the user?”
- Validate Scope (PMP): The process of formalizing acceptance of the completed project deliverables. It is primarily concerned with acceptance of the deliverables, whereas Quality Control is concerned with correctness.
- Fitness for Use: A PMP quality concept. Even if a product meets all technical specifications, it must be practical and usable for the end customer to be considered “High Quality.”
Section 2: The “Go/No-Go” Decision and the Cutover Plan
The Friday before the scheduled launch, a tension-filled “Go/No-Go” meeting was convened on the virtual bridge. Participants from four continents logged in: Tim John (Norwalk), Jason Vance (New Orleans), Mate Rossi (London), Daniel Silva (Mexico), and the full 7Pro leadership team in Delhi.
Kapil Mehta projected the Final Release Checklist onto the screen. “We have achieved a 100% pass rate on the Security regression testing. We have 92% user satisfaction from the Canadian UAT. The remaining 8% are ‘Minor Cosmetic’ issues—the animation speed and font size adjustments—that we have collectively agreed to move to the Day 2 Support Backlog.”
“What about the Canadian tax rounding error that we found in Sprint 0?” Mate Rossi asked, his voice sharp and precise as usual. “Is that 100% resolved?”
“Verified and signed off by the Chartered Accountants yesterday, Mate,” Mohd Tariq confirmed, referencing the RTM (Image 0.png).
Tim John rubbed his temples. “The Board is watching this rollout. The market entry is critical. Do we have the confidence? Kapil, give me the final status.”
Kapil looked at his team. “We have the technical confidence, the functional sign-off, and a detailed Cutover Plan. We are a ‘Go’.”
“Then I’m a ‘Go’ from Canada’s perspective,” Jason added.
“I am a ‘Go’ from a release integrity perspective,” Mate said.
“Kapil,” Tim John said, “execute the Cutover Plan. You have authorization.”
Section 2 Breakdown: The PMP & ITIL Lens
- Transition and Handover (PMP): The formal process of moving the project from the “Project Team” (7Pro India) to the “Operations/Maintenance Team” (New Orleans).
- Cutover Plan (ITIL 4): A highly detailed, hour-by-hour schedule of tasks required to move from the old state to the new live Production environment.
- Change Management (ITIL 4): The formal “Go” from the stakeholders (Tim, Mate, Jason) acts as the final approval from the Change Advisory Board (CAB) to push the code. This ensures the organization has formally accepted the risk of the launch.
Section 3: The “Day 2” Reality – Hypercare and Incident Management
The “Cutover” happened at 4:00 AM Toronto time (1:30 PM Delhi time). By 10:00 AM in Canada, thousands of users were downloading the QT Money app. Back in the 7Pro ODC, the atmosphere wasn’t one of celebration; it was one of intense concentration. The team had transitioned into Hypercare Mode.
“We have a spike in ‘Login Failures’ from the Quebec region,” Shakira shouted, her eyes fixed on the real-time monitoring dashboard. “It looks like the French language localization is clipping the ‘Submit’ button on smaller iPhone screens. Users can’t tap ‘Enter’!”
“That’s a P1 Incident,” Kapil Mehta said, standing at the center of the room. “Tariq, we are officially in the Warranty phase. Forget the backlog for a moment. We need a hotfix for the Quebec UI immediately. We keep this ‘War Room’ open until the incident rate drops below the threshold defined in our SLA (Service Level Agreement).”
For the next 72 hours, the team didn’t act as “Project Developers.” They acted as Service Desk Support. They were ensuring that the product they built actually delivered the Utility (what it does) and Warranty (how it performs) promised to the stakeholders.
Section 3 Breakdown: The PMP & ITIL Lens
- Hypercare: A period of elevated support immediately after a system go-live to ensure stability. It is the bridge between the “Project” and “Operations.”
- Incident Management (ITIL 4): The process of restoring normal service operation as quickly as possible to minimize the impact on business operations. A “P1” (Priority 1) incident requires immediate, all-hands-on-deck attention.
- Utility and Warranty (ITIL 4): * Utility: The functionality (e.g., “The app allows me to transfer money”).
- Warranty: The assurance that it works when needed (e.g., “The button is visible and the app doesn’t crash”). A successful launch requires both.
Section 4: Closing the Project – The Final Handover
A week after the Quebec hotfix, the “QT Money” app had reached a state of stability. The incident rate had flattened to nearly zero, and the “War Room” in Delhi finally began to quiet down. Kapil Mehta sat at his desk, but he wasn’t writing code—he was writing the Final Project Report.
“Tariq,” Kapil said, looking over the final metrics. “We’ve officially transferred the ‘Ownership’ of the code repository and the technical documentation to the New Orleans Maintenance team. The transition is complete.”
The Closing phase of a PMP project isn’t just about stopping work; it’s a formal process. Kapil systematically checked off the last requirements:
- Release of Resources: The junior developers, Shakira and Deepak, were formally released back to the 7Pro “Resource Pool” for their next assignments.
- Archiving Records: All Sprint data, the RTM, and the Issue Logs were moved to the Organizational Process Assets (OPAs) library.
- Final Acceptance: The most important step. Kapil received a digitally signed document from Tim John in Norwalk, formally accepting the project deliverables and authorizing the final payment to 7Pro India.
“We did it,” Mohd Tariq said, closing his laptop for the first time in eighteen months. “From a blank page in Delhi to a live banking app in Canada.”
Kapil smiled. “The project is officially Closed. Now, let’s archive the Lessons Learned so we don’t make the same mistakes in Phase 2.”
Section 4 Breakdown: The PMP & ITIL Lens
- Administrative Closure (PMP): The formal process of finalizing all activities across all Project Management Process Groups to formally complete the project or phase.
- Lessons Learned Register: A core OPA. This document ensures that the knowledge gained during the QT Money project (like the Budapest driver issue or the Delhi blackout) is preserved for future 7Pro teams.
- Release of Team (Resource Management): In a functional or matrix organization, the PM must formally release the staff so they can be reallocated to other value-generating work.
Section 5: Summary – What Did We Learn?
- UAT is the “Ultimate Truth”: Your code is only as good as the user’s ability to use it. Always map UAT results back to the RTM.
- The “Go/No-Go” is a Shield: Use a data-driven checklist to get formal stakeholder approval. This prevents “finger-pointing” if issues arise post-launch.
- Hypercare is the Safety Net: Never walk away the moment the “Deploy” button is pressed. Budget for 72+ hours of intensive support (Warranty).
- Closing is a Process, Not an Event: Releasing resources and archiving knowledge are critical for the long-term health of the company.
- P1 Incidents are Lessons: Every “Quebec Login Spike” is an opportunity to improve your testing protocols for the next project.
What’s Next in the Series?
The journey of 7Pro and QT Money is a testament to the power of structured Project Management. We have covered the “Baptism by Fire,” the “Black Swan” of the blackout, and the “Finish Line” of the Canada Go-Live.
Series Wrap-Up: The 7Pro Playbook – A Masterclass in PMP & ITIL. We will summarize all 9 articles into a single, high-value “Cheat Sheet” for your PMP Exam preparation!
