Article 2: The Global Org Chart – Who Actually Owns Quality?
Section 1: The “Meticulous Mate” and the London Lockdown
The “P1” outage from the previous night had been resolved, but the aftershocks were still vibrating through the 7Pro ODC. It was 4:30 PM in Delhi, and Kapil Mehta was finally nursing a lukewarm tea when a new meeting invite hit his inbox: “Global QA Strategy & Entry Criteria – MANDATORY ATTENDANCE.”
The organizer? Mateo “Mate” Rossi, the QA Lead in London.
“Tariq,” Kapil called out to Mohd Tariq, who was adjusting a server configuration on his screen. “Are you ready for the London Lockdown?”
Tariq looked up, a weary smile on his face. “Mate doesn’t want a handover, Kapil. He wants a deposition. He just sent a 45-page ‘Standard Operating Procedure’ document. He says if we don’t follow his ‘Quality Gates,’ he won’t let a single line of 7Pro code into the UK testing environment.”
By 6:30 PM, the global bridge was live.
“Let’s be perfectly clear,” Mate’s voice was sharp, cutting through the static of the London-to-Delhi line. “In the UK, we do not ‘wing it.’ I understand Tim John wants speed, and I know Jason Vance in New Orleans wants ‘Agile everything,’ but my team is responsible for the integrity of the QT Money portal. I will not have my testers wasting time on builds that aren’t ‘Entry-Ready.'”
“Mate, buddy, come on!” Jason Vance’s voice boomed from LA. “We’re doing Scrum! We don’t need 45 pages of documentation. We need a backlog and a sprint. Let’s get moving!”
“Agile is not an excuse for anarchy, Jason,” Mate snapped back. “I see 10 developers in India, but I don’t see a RACI Matrix. Who is Accountable if the Mexico load balancer isn’t configured for the new code? Who is Responsible for the Budapest server patches? Right now, everyone is talking, but no one is ‘owning.'”
Kapil realized the technical fire was out, but a Governance Crisis had begun. If he couldn’t bridge the gap between “Agile Jason” and “Waterfall Mate,” the project would stall before the first sprint even started.
Section 1 Breakdown: The PMP & ITIL Lens
- The Quality Performance Domain: In PMBOK 7, Quality isn’t just a “phase” at the end; it’s a constant performance domain. Mate is demanding Quality Metrics and Entry Criteria—the specific conditions that must be met before work can move from “Development” to “Testing.”
- RACI Matrix (Accountability vs. Responsibility): This is the “Who’s Who” of project management.
- Responsible: The person doing the work (e.g., the 7Pro Devs).
- Accountable: The one person who must answer for the success or failure (e.g., the SDM, Kapil).
- Tailoring (Conflict Management): We are seeing a clash of methodologies. Jason wants Adaptive (Agile); Mate wants Predictive (Waterfall). Part of a Project Manager’s job is “Tailoring”—finding a hybrid middle ground that satisfies the need for speed and the need for documentation.
Section 2: The “RACI” Tug-of-War
Kapil Mehta took a deep breath. He could hear the tension in the silence coming from the London and LA lines. If he didn’t intervene now, Mate would block the environment access, and Jason would start a “shadow” development track just to prove a point.
“Mate, Jason,” Kapil said, leaning into his microphone. “I hear both of you. Mate, you need to know that nothing is going to break your ‘Quality Gates.’ Jason, you need to know that we aren’t going to spend three weeks writing a manual before we write code. Mohd Tariq, pull up the Draft RACI Matrix on the screen share.”
Tariq clicked a button, and a grid appeared.
“Okay,” Kapil continued. “Let’s define the ‘A’—the Accountability. For the Budapest Server patches, Mellissa Varga is Responsible (R), but Rob Miller in Jersey is Accountable (A). If the patch fails, Rob owns the fix. But for the Code Quality itself, I am Accountable, and Tariq is Responsible.”
“What about the Load Balancer?” Daniel Silva’s voice piped up from Mexico City. “I’m in Mexico. If I’m ‘Responsible’ for the configuration, who ‘Consults’ me before Jason’s team changes the API endpoints?”
“That’s exactly it, Daniel,” Kapil noted. “You are Consulted (C) during the Sprint Planning. We don’t change a single port without your sign-off in the meeting. And Mate, you and your UK team are Informed (I) the moment the build is ready for the gate. You don’t have to check the logs; the system will tell you.”
Mate Rossi was quiet for a moment. He was scanning the grid. “It’s a start, Kapil. But I want to see a specific row for the Definition of Done (DoD). Who signs off that the code is ‘Testing-Ready’ before it hits London?”
“That would be me,” Jason Vance said, his voice softening. “I’ll own the sign-off for the Dev-Ready status. But Mate, if I sign it, you have to promise your team starts the regression testing within two hours. No more ‘waiting for the morning’ in London.”
The “Tug-of-War” was shifting. They weren’t fighting about code anymore; they were negotiating a Social Contract.
Section 2 Breakdown: The PMP & ITIL Lens
- Definition of Done (DoD): In Agile and PMP 7th Edition, the “Definition of Done” is a critical agreement between the team and stakeholders. It prevents the “but it works on my machine” excuse.
- RACI Logic: * Consulted (C): Two-way communication. We ask Daniel before we act.
- Informed (I): One-way communication. We tell Mate when we are finished.
- Conflict Resolution (Negotiating): Kapil used the RACI as a neutral tool to move the conversation from “Personalities” to “Processes.” This is a key skill in the Team Performance Domain.
Section 3: The “Ghost” Patch – 4:00 AM in Budapest
The digital ink on the RACI was barely dry when the first crack appeared in the “Social Contract.”
It was 4:00 AM in Budapest. Mellissa Varga sat in the dimly lit server room, the hum of thousands of fans providing the soundtrack to her shift. She was applying a critical security patch to the “Heartbeat” monitor—the same one that had caused the P1 outage forty-eight hours earlier.
According to the new RACI, Rob Miller (Jersey City) was “Accountable” for this patch, and Daniel Silva (Mexico City) was supposed to be “Consulted” because the patch would momentarily reset the load balancer connections.
But Daniel was at a late lunch in Mexico City, and Rob was in a deep sleep in New Jersey.
“I cannot wait,” Mellissa whispered to herself. “If I don’t apply this now, the automated audit script will lock the ports again in thirty minutes.” She hit the ‘Execute’ button.
Back in Delhi, a notification pinged on Mohd Tariq’s screen. “ALERT: Budapest Node 01 – UNEXPECTED REBOOT.”
“Kapil!” Tariq shouted across the ODC. “Someone is rebooting the primary server! No one called it out on the bridge! No one opened a Change Request!”
Kapil grabbed his headset. “Daniel? Are you there? Did you authorize a reboot?” “I’m here,” Daniel’s voice came through a mouthful of food. “I didn’t authorize anything. I’m looking at the F5 logs… wait, the traffic is dropping! Who is touching the server?”
The “RACI” was being ignored. Because the patch was “Emergency,” Mellissa had bypassed the Consulted and Informed protocols. To the 7Pro team in India, it looked like another DDoS attack. To Daniel in Mexico, it looked like a server failure.
“Get Mellissa on the line!” Kapil ordered. “And someone wake up Rob. If he’s ‘Accountable,’ he needs to know his server is currently a brick.”
Section 3 Breakdown: The PMP & ITIL Lens
- Change Management (ITIL 4): This was an “Emergency Change.” ITIL defines a specific path for these, but even an emergency change requires a “Post-Facto” notification. Mellissa failed the Communication aspect of the process.
- RACI Failure: This is a classic real-world scenario. A document is only as good as the Culture that supports it. Mellissa operated in a “Silo,” ignoring the Consulted (C) and Informed (I) lines because she felt the technical urgency outweighed the process.
- Risk Management (PMP Domain: Uncertainty): This reboot represented a “Known-Unknown.” The team knew patches were coming, but they didn’t have a Change Window synchronized across all time zones.
Section 4: The “I Told You So” – Closing the Quality Gate
The bridge line was no longer a professional meeting; it was a digital crime scene. Rob Miller (NJ) had been patched in, his voice sounding gravelly and defensive after being woken up.
“Mellissa had to make a call, okay?” Rob snapped. “The audit script doesn’t wait for Mexico to finish lunch or India to check their RACI. She protected the environment.”
“She protected the environment by crashing the heartbeat?” Kapil Mehta shot back, his calm finally wearing thin. “My night shift team just spent two hours debugging a ‘ghost’ reboot. That’s ten man-hours wasted because the Consulted line in our RACI was ignored.”
“And this is exactly my point,” Mateo “Mate” Rossi’s voice cut through the noise from London. He sounded almost satisfied. “If a simple security patch can bypass the entire communication framework, how can I trust 7Pro to manage a complex code deployment next week? Tim, I’m officially closing the Quality Gate. No code moves to the UK test environment until we have a hard-coded Change Management workflow in ServiceNow that locks the servers during a deployment window.”
Tim John (Norwalk) sighed. The sound of his pen tapping against a desk was audible. “Kapil, Mate is right. We have the people, and we have the names on a chart, but we don’t have the Integration. 7Pro needs to show me how they will enforce the RACI using tools, not just spreadsheets.”
Kapil looked at Mohd Tariq. Tariq nodded slowly, already opening a new tab. “We can do that, Tim. We’ll integrate the RACI directly into the ServiceNow Change Module. If Mellissa or anyone else tries to hit ‘Execute’ without an approved ticket, the system will flag the ‘Consulted’ parties automatically. We’ll move from a ‘Social Contract’ to a ‘System Contract.'”
The battle for Article 2 ended not with a victory, but with a challenge: Automate or Fail.
Section 4 Breakdown: The PMP & ITIL Lens
- Work Authorization System (PMP): This is a formal PMP concept. It is a sub-component of the overall Project Management System that ensures work is done at the right time and in the right sequence. Kapil is proposing a digital version of this.
- The Feedback Loop (Agile/PMP): This crisis acted as a “Retrospective” in real-time. The team identified a process failure and immediately proposed a technical solution to prevent recurrence.
- Quality Assurance vs. Quality Control: Mate is focused on Quality Assurance (QA)—the process and the “Gates.” He doesn’t want to find bugs later; he wants to prevent the circumstances that create bugs.
Summary of Article 2: The Global Org Chart
In this second installment, we’ve moved from the adrenaline of a crash to the heavy lifting of governance.
- The Conflict: Agile vs. Waterfall mindsets (Jason vs. Mate).
- The Crisis: A “Ghost Patch” that ignored the newly created RACI.
- The Resolution: The move toward automating the Change Management process.
- The PMP/ITIL Link: We’ve explored the RACI Matrix, Definition of Done (DoD), and Change Management workflows.
:%20The%20Handover%20Crisis%20&%20The%20PIN){kind=link}
){kind=link}