SaatPro
Where Technology Meets Clarity
Section 1: The “New Orleans” Wishlist
It was 8:00 PM in Delhi, and the 7Pro ODC was buzzing. The “Ghost Patch” crisis in Budapest had been resolved, but a new storm was brewing. Jason Vance (New Orleans) had just shared his screen during the first official Sprint Planning session.
“Alright, team!” Jason’s voice was full of Bayou energy. “I’ve got the ‘QT Money 2.0’ vision board ready. We need the new biometric login, the crypto-wallet integration, and the Canadian tax-compliance module ready for testing by the end of the month. I’ve dropped 45 items into the backlog. Let’s get these into Sprint 1 and start cooking!”
Mohd Tariq stared at the screen, his face turning pale. He scrolled through the “backlog.” Most of the items were single sentences: “Make the login faster” or “Add Canada support.” There were no User Stories, no Acceptance Criteria, and definitely no technical documentation for the Canadian tax laws.
“Jason,” Tariq said, his voice hesitant. “This isn’t a backlog. This is a wishlist. We are in Sprint 0. We can’t commit to ‘Sprint 1’ because these items aren’t ‘Ready.’ According to our Definition of Ready (DoR), we need the API specs from the UK team and the security parameters from Rob in NJ.”
“Tariq, we’re Agile!” Jason laughed. “We figure it out as we go! That’s the whole point of the 7Pro partnership—speed!”
Kapil Mehta leaned into the camera. “Jason, speed without direction is just a fast way to go in the wrong direction. If we start coding ‘Biometric Login’ today without Mate Rossi’s (London) security sign-off, Mate will just reject the build at the Quality Gate next week. We’ll be doing double the work.”
The battle line was drawn: Agile Speed vs. PMP Discipline.
Section 1 Breakdown: The PMP & ITIL Lens
- Sprint 0 (The Preparatory Phase): While not officially a “Scrum” term, in PMP and practical IT projects, Sprint 0 is used to set up the environment, the Product Backlog, and the Definition of Ready (DoR). It’s about building the “tracks” before the “train” starts moving.
- Definition of Ready (DoR): This is a critical PMP/Agile artifact. It is a set of criteria that a User Story must meet before it can be pulled into a Sprint. If a story is “vague,” it fails the DoR and stays in the backlog.
- Scope Management (PMP Domain: Process): Jason is attempting to introduce “Scope Creep” by adding high-complexity items without a formal Decomposition (breaking them down into smaller, manageable tasks).
Section 2: The “Backlog Doctor” – Scrubbing the Wishlist
By the time the call with New Orleans ended, Mohd Tariq was already drafting a spreadsheet. He knew that if the 7Pro developers started working on “Biometric Login” based on Jason’s one-sentence description, they would produce code that Mate Rossi (London) would reject on sight.
“Kapil,” Tariq said, pointing at his screen. “I’m looking at the ‘Canadian Tax Module’ story. It just says ‘Apply GST/HST logic.’ Which provinces? What’s the rounding rule? If we don’t have the Functional Specifications, we aren’t coding—we’re guessing.”
“Mate Rossi has the specs,” Kapil Mehta replied, “but he’s refusing to release them until we provide a Technical Design Document (TDD) for the entire integration. It’s a deadlock. Mate won’t give us the ‘What’ until we prove we know the ‘How,’ and we can’t know the ‘How’ until he gives us the ‘What.'”
Kapil picked up the phone. It was time for a “Side-Bar” negotiation with London.
“Mate,” Kapil began when the UK lead answered. “We’re in Backlog Refinement. You’re worried about 7Pro breaking the audit trail. I get that. But if you hold back the tax specs, Jason is going to force a ‘Go-Live’ date that we can’t hit. If you give Tariq the API endpoints now, we will build the TDD during Sprint 0 as a Spike.”
“A Spike?” Mate paused. The PMP terminology seemed to calm him. “Fine. I’ll give you the endpoints for the Canadian gateway. But if the Acceptance Criteria aren’t met to the letter, the build doesn’t leave the ODC.”
Section 2 Breakdown: The PMP & ITIL Lens
- Backlog Refinement (Grooming): This is the ongoing process of adding detail, estimates, and order to items in the Product Backlog. Tariq is acting as the “Backlog Doctor” to ensure the team only works on “Healthy” stories.
- The Spike (Agile/PMP Technique): A Spike is a short time-boxed effort to research a technical or functional uncertainty. Instead of committing to a full feature, the team commits to a “Spike” to understand the Canadian tax laws.
- Acceptance Criteria: These are the specific conditions that a software product must satisfy to be accepted by a user, customer, or other stakeholder (like Mate). In PMP, this is part of Validating Scope.
Section 3: The Sprint 0 “Artifact” – The Definition of Ready (DoR)
The clock was ticking toward the end of the week. To stop the cycle of “Guess-Coding,” Kapil and Tariq sat down to create the project’s most important document for Sprint 1: The Definition of Ready (DoR) Checklist.
“From now on,” Kapil announced to the team, “no story moves from the Backlog into a Sprint unless it hits these four marks:
- Independent: Can it be worked on without waiting for another story?
- Negotiable: Is there room for the devs to discuss the ‘How’ with Jason?
- Small: Can it be finished in one sprint?
- Testable: Do we have the Acceptance Criteria from Mate?”
Deepak and Shakira, the night-shift leads, nodded. This was their shield. If Jason tried to throw a vague “Make it faster” ticket at them at 2:00 AM, they could now say, “This fails the DoR. Please refine.”
Section 3 Breakdown: The PMP & ITIL Lens
- The INVEST Mnemonic: This is a classic PMP/Agile tool for evaluating the quality of User Stories (Independent, Negotiable, Valuable, Estimable, Small, Testable).
- Team Charter (PMP Domain: People): By agreeing on the DoR, the team is establishing Ground Rules. This reduces friction and sets clear expectations between the US Product Owner and the India Development team.
Section 4: The Shield – Defending the Velocity
The Friday evening sync was the moment of truth. Jason Vance (New Orleans) dialed in, expecting to see a screen full of “In-Progress” tickets. Instead, he saw Kapil Mehta’s shared screen displaying a clean, four-point checklist: The Definition of Ready (DoR).
“What is this, Kapil?” Jason’s voice lost its playful edge. “We’re supposed to start the Sprint on Monday. Why are 80% of the Canadian tax stories still sitting in the ‘Draft’ column?”
“Because they aren’t ‘Ready,’ Jason,” Kapil said firmly. “Look at Story #402: ‘Canadian Compliance.’ There are no rounding rules for the PST (Provincial Sales Tax). If we start coding this now, we’ll hit a wall by Wednesday, and our Velocity will tank. We’d be delivering ‘Dark Matter’—work that looks like progress but adds no value.”
Jason sighed, the sound of a man who had a VP of Finance breathing down his neck. “I have a deadline, Kapil. I can’t wait for Mate Rossi in London to decide he’s ‘satisfied’ with the documentation.”
“Actually,” Mohd Tariq interjected, “we used the Spike we agreed on with Mate. We’ve already mapped the API endpoints. If you give us thirty minutes to finalize the Acceptance Criteria for the rounding rules right now, we can move these stories to ‘Ready’ before the shift ends. We aren’t slowing you down, Jason—we’re making sure we don’t have to stop later.”
The tension broke. Jason realized the “Shield” wasn’t a barrier; it was a filter. By the end of the hour, the backlog was scrubbed, the “vague” stories were parked, and 7Pro had a Sprint 1 plan that was actually achievable.
The battle of Sprint 0 was won.
Section 4 Breakdown: The PMP & ITIL Lens
- Velocity (Agile Metric): Velocity is the measure of the amount of work a team can tackle during a single Sprint. By using a DoR, Kapil protected the team’s velocity from being dragged down by “Blocked” or “Vague” tasks.
- Definition of Done vs. Definition of Ready: * DoR (Entrance): Can we start it? (The focus of Article 3).
- DoD (Exit): Is it finished correctly? (The focus of Mate Rossi).
- Servant Leadership: Kapil acted as a Servant Leader by “removing impediments.” He didn’t just tell the team to work harder; he fixed the broken process that was making their work impossible.
Summary of Article 3: Sprint 0 & The Backlog Battle
We’ve now crossed the bridge from planning into the first stages of execution.
- The Conflict: Speed vs. Stability (Jason vs. Tariq).
- The Tool: The INVEST criteria and the DoR Checklist.
- The PMP/ITIL Link: We’ve mastered Backlog Refinement, Spikes, and Scope Validation.
