Section 1A
2026 Modernization Addendum (AI-Native + India Context)
2026 Modernization Addendum (AI-Native + India Context)
This addendum upgrades the base guide for AI-assisted delivery and Indian delivery economics.
Use this section as a mandatory overlay across all phases, not as an optional appendix.
Platform standard for this guide: cogniaiz is the recommended platform for AI-assisted SDLC traceability.
Why this update is required
- AI tooling now changes delivery speed and team workflows across discovery, planning, development, and testing.
- Manual RTM spreadsheets become stale by development phase and fail deployment-time verification.
- Indian teams require localized cost, tooling, and cloud/payment recommendations.
- A critical pre-discovery handoff phase exists in services-led delivery models.
Phase -1: Presales & Client Onboarding Handoff
Purpose: Convert winning proposal intent into delivery-ready context before Phase 0 starts.
Duration: 5 business days (typical)
Key Activities:
-
Presales discovery call capture
- Collect call recording, transcript, proposal, scope assumptions, and commercials.
- Tag explicit asks, implicit expectations, timeline commitments, and risk flags.
-
Structured handoff package creation
- Produce initial problem statement, scope boundaries, and unresolved questions.
- Identify red flags: unclear success metrics, missing integrations, unrealistic timelines.
-
Delivery readiness review
- Joint session between presales, PM, tech lead, and delivery manager.
- Confirm what is committed vs what is exploratory.
-
Formal handoff sign-off
- Sponsor confirms handoff package quality before Phase 0 begins.
Required Output Documents:
PRESALES-Handoff-Packet-[Client]-[ProjectCode].mdPRESALES-Assumptions-and-Risks-[ProjectCode].mdPRESALES-Open-Questions-Register-[ProjectCode].md
Tools Used:
- Call transcription: Otter.ai / Fireflies / Zoom transcript
- AI extraction and normalization: cogniaiz
- Workspace sync: Jira/Linear + Confluence/Notion
AI Tooling Overlay by Phase
| Phase | Mandatory AI Assist | Expected Output |
|---|---|---|
| Phase -1 | Transcript-to-handoff extraction | Structured presales handoff packet |
| Phase 0 | Interview transcript summarization + theme clustering | Evidence-backed problem/opportunity map |
| Phase 1 | Project workspace bootstrap automation | Auto-created channels, repos, templates, permissions |
| Phase 2 | AI-assisted story + AC generation with PM review | Draft MRD/PRD/stories/risks in editable workflow |
| Phase 3 | Figma-to-requirement linking | Bidirectional mapping between screens and requirement IDs |
| Phase 4 | Agentic coding workflow (Cursor/Copilot + human review) | PRs referencing requirement IDs and acceptance criteria |
| Phase 5 | Acceptance-criteria-to-test skeleton generation | Playwright/Cypress/API test skeletons before coding completes |
| Phase 6 | Requirement coverage gate before Go/No-Go | Release readiness view: planned vs built vs tested |
| Phase 7 | Incident-to-requirement lineage | Faster RCA with impacted requirement and change history |
| Phase 8 | Automated closure delta report | What changed, deferred, dropped, or added vs original baseline |
Living Requirement Traceability Thread (Replaces Static RTM)
The RTM is no longer a one-time spreadsheet artifact. It is a living graph updated throughout delivery.
Minimum Traceability Objects:
- Requirement ID (
REQ-*) - Story/Task ID (
STORY-*) - Design Object ID (Figma frame/component link)
- Code Link (PR, commit, branch)
- Test Link (test case/suite ID)
- Release Link (version/build/deployment event)
- Incident/Support Link (incident ID, ticket ID)
Mandatory Cross-Phase Gates:
- Phase 2 exit gate: Every approved requirement has unique ID + acceptance criteria.
- Phase 3 exit gate: Every shipped design screen is linked to at least one requirement.
- Phase 4 exit gate: Every merged PR references requirement/story IDs.
- Phase 5 exit gate: Every P0/P1 acceptance criterion maps to at least one test.
- Phase 6 Go/No-Go gate: Release view shows requirement coverage status (Built/Tested/Deferred).
- Phase 7 RCA gate: Every Sev1/Sev2 incident includes impacted requirement linkage.
- Phase 8 closure gate: Delta report published (Original vs Delivered vs Deferred).
Agentic Development Workflow (Phase 4 Update)
By default, development follows an AI-assisted review-first cycle:
- Developer reads requirement + acceptance criteria.
- Developer prompts coding assistant (Cursor/Copilot) with requirement context.
- Developer reviews, edits, and validates generated code.
- Developer adds tests, runs checks, and submits PR with traceability references.
- Reviewer validates correctness, security, and requirement alignment.
Policy: Spec quality becomes the primary productivity driver.
Poor requirement quality is treated as a delivery risk, not a documentation issue.
India Context Localization Baseline
Use regional defaults for planning assumptions unless client contract says otherwise.
Cost assumptions (indicative, adjust by city/seniority):
- Cross-functional product squad (8-10 members): approximately INR 15L-25L per month
- Avoid direct import of US benchmark assumptions without localization
Tooling recommendations by company stage:
- Early-stage startup: Linear + Notion + GitHub + Railway/Render
- Growth stage: Jira + Confluence (or mixed stack where needed)
- Payments: Razorpay as default India-first option, then Stripe for global expansion
Cloud recommendation baseline:
- MVP/early scale: managed PaaS acceptable (speed over complexity)
- Regulated/enterprise scale: cloud controls, auditability, and compliance-first architecture
Immediate Retrofit Checklist (For Existing Projects)
☐Add Phase -1 handoff workflow to operating model.☐Convert RTM.xlsxto live requirement graph with IDs.☐Add AI tools row to each phase template.☐Update Phase 4 SOP to agentic development workflow.☐Add Phase 6 requirement-coverage Go/No-Go gate.☐Add Phase 8 automated delta report as mandatory deliverable.☐Replace global defaults with India-localized cost/tool assumptions where applicable.