Skip to lesson
Exit
Reconstruct the enterprise SDLC1 / 3

1 min lesson

The two-minute 'how a feature ships' narration

Explain the practical point behind "Adapt the system names to the account and keep the structure."

Step 1 of 3

The most powerful move in a discovery call is to narrate a feature's journey through their lifecycle, name the systems and the queues, then point at exactly where Cursor removes friction.

Here's the canonical version. Adapt the system names to the account and keep the structure.

Learn more

Full explanation

Why this narration wins

  1. 1Plan. A product manager files a ticket in Jira with acceptance criteria. It sits in the backlog until a sprint pulls it. (Queue #1.)
  2. 2Design. For anything non-trivial, an architect writes or updates an ADRArchitecture Decision Record. A short doc capturing one architecture decision and the reasoning behind it. Press Enter for the full definition. in Confluence. The decision is now an artifact, a context source the agent should read via MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. Press Enter for the full definition..
  3. 3Build. An IC dev opens the ticket in Cursor. With Jira, GitHub and Confluence bridged, the agent has the ticket, the code and the ADRArchitecture Decision Record. A short doc capturing one architecture decision and the reasoning behind it. Press Enter for the full definition. in context. It drafts the change. The dev keeps judgment and shapes the PR.
  4. 4Test / CI. The PR triggers Jenkins; tests run, artifacts land in Artifactory. BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. Press Enter for the full definition. reviews the PR in parallel so a human reviewer starts with focused findings rather than a cold diff. (Queue #2: human review.)
  5. 5Release. A change record is filed in ServiceNow; the CABChange Advisory Board. A group that reviews and signs off on higher-risk production changes before they ship. Press Enter for the full definition. approves; the change ships through the golden path. Separation of duties holds, because the author isn't the approver.
  6. 6Operate. Datadog watches it in production. If it pages, an incident opens in PagerDuty. (Forward stream ends; return loop begins.)
  7. 7Return loop. The postmortem produces corrective actions: a missing test, a config hardening, a runbook fix. Those re-enter at Build as low-blast-radius work, ideal for an agent and the whole chain is linked as evidence.
Why this narration wins

It proves you understand their machine. It names the two queues where time actually leaks (sprint pull and human review), shows the artifact graph in motion and closes the circuit by ending on the return loop, your beachhead. You've shown separation of dutiesNo single person can author, approve and deploy the same change. The core control AI autonomy has to respect. Press Enter for the full definition. stays intact and governance is respected. You did it without a single slide.

Where Cursor removes friction in the narration
Build
Agent reasons over ticket + ADRArchitecture Decision Record. A short doc capturing one architecture decision and the reasoning behind it. Press Enter for the full definition. + code via MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs. Press Enter for the full definition., producing org-correct drafts
Human review (Queue #2)
BugbotCursor's automated PR reviewer that posts inline findings and can push fix commits from isolated VMs. Press Enter for the full definition. triages PRs before humans look and drains the backlog
Return loop
Corrective changes drafted fast, fully evidenced - the safe beachhead
The closing line

"Notice I never proposed removing a single control or a single human judgment call. We drained the two queues where your time actually leaks and we started in the return loop, where the work is safest."

Learn more

Optional practice

Practice: The two-minute 'how a feature ships' narration

QWhy should the two-minute narration deliberately END on the return loop rather than on Release?