Full-stack NPI (New Product Introduction) gate tracking tool with: - Express/TypeScript API with PostgreSQL - React/Vite/Mantine frontend - 13-gate process (G0-G12) with 4 product categories - RACI matrix auto-population from templates - File attachments with preview (images, PDFs, text) - Kanban board, Gantt/timeline views - Docker Compose orchestration Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
598 lines
25 KiB
SQL
598 lines
25 KiB
SQL
-- Evidence requirements and failure modes from Sheet1 (reference data)
|
||
-- Stored as comments for now; can be added to gate_steps table later
|
||
|
||
-- G0 | Product
|
||
-- Instructions: Create/Update registry; confirm Category III; record triggers; create tailoring doc; name owners (Product, Tech Lead, Sponsor, Commericial owner); ensure cost controls exist; collect required sign-off
|
||
-- Evidence: Registry entry link; Tailoring doc link; Trigger fields completed; Owner list; Cost control plan link
|
||
-- Failure modes: Missing owners; wrong category; triggers not captured; tailoring not approved before work starts
|
||
|
||
-- G0 | Product
|
||
-- Instructions: Log request; coordinate inputs from Tech Lead, Compliance, Security/IT, Legal, Finance, Commericial, Procurement, Client services/Support.
|
||
-- Evidence: Meeting notes/approvals captured; links to reviewer comments
|
||
-- Failure modes: Chasing approvals too late; unclear who must sign
|
||
|
||
-- G0 | Tech Lead
|
||
-- Instructions: Validate feasibility at high level; identify dependencies (connectors/data); propose kill switch approach; outline monitoring needs.
|
||
-- Evidence: Feasibility notes; dependency list; kill switch concept; monitoring notes
|
||
-- Failure modes: Underestimating complexity; connectors discovered late; no rollback/kill switch
|
||
|
||
-- G0 | Sponsor
|
||
-- Instructions: Confirm business intent and approve proceeding; commit to stop/go decisions and resourcing expectations.
|
||
-- Evidence: Recorded sponsor approval (email/Planner approval)
|
||
-- Failure modes: Sponsor not engaged; later objections
|
||
|
||
-- G0 | Compliance
|
||
-- Instructions: Confirm data class + intended boundaries implications; flag policy constraints; specify required safety/data controls.
|
||
-- Evidence: Compliance trigger assessment note
|
||
-- Failure modes: Data sensitivity missed; no policy requirements captured
|
||
|
||
-- G0 | Security/IT
|
||
-- Instructions: Flag connector/tool permission risks; confirm environment/access constraints; identify security review needs.
|
||
-- Evidence: Security trigger assessment note
|
||
-- Failure modes: Connectors approved informally; excessive permissions
|
||
|
||
-- G0 | Legal
|
||
-- Instructions: Identify waiver/MSA/contract needs; flag legal no-go constraints; confirm disclaimer/terms requirements.
|
||
-- Evidence: Legal trigger assessment note
|
||
-- Failure modes: Legal brought in late; waiver/MSA blocks near go-live
|
||
|
||
-- G0 | Finance
|
||
-- Instructions: Confirm budgeting approach; set expectation for cost limits/alerts; identify billing readiness needs later.
|
||
-- Evidence: Cost governance note
|
||
-- Failure modes: Budgets not set; no one owns spend
|
||
|
||
-- G0 | Commericial
|
||
-- Instructions: Confirm sell model intent; assign owner for PPPP; flag early commercial viability concerns.
|
||
-- Evidence: Commercial intent note
|
||
-- Failure modes: No commercial owner; pricing considered too late
|
||
|
||
-- G0 | Procurement
|
||
-- Instructions: Confirm contract storage location and renewal reminder mechanism; align with procurement workflow.
|
||
-- Evidence: Contract repository path + reminder method
|
||
-- Failure modes: Auto-renewal surprises; contracts stored with individuals
|
||
|
||
-- G0 | Client services
|
||
-- Instructions: Confirm operational impact; flag implementation/training dependencies and timing concerns.
|
||
-- Evidence: Ops impact note
|
||
-- Failure modes: Implementation not ready at launch
|
||
|
||
-- G0 | Support
|
||
-- Instructions: Flag supportability concerns early; confirm whether SLA/24x7 support is required.
|
||
-- Evidence: Support early input note
|
||
-- Failure modes: Support resourcing not considered until late
|
||
|
||
-- G1 | Product
|
||
-- Instructions: Define buyer/client use case; define success criteria; draft intended use boundaries (with Compliance/Legal); capture feasibility notes with Tech Lead.
|
||
-- Evidence: Use case doc/link; Success criteria list; Boundaries statement
|
||
-- Failure modes: Use case vague; success criteria not measurable; boundaries missing
|
||
|
||
-- G1 | Sponsor
|
||
-- Instructions: Approve ideation to proceed based on use case, success criteria, boundaries and feasibility.
|
||
-- Evidence: G1 approval record
|
||
-- Failure modes: Approvals informal; later reversal
|
||
|
||
-- G1 | Commericial
|
||
-- Instructions: Confirm plausible monetisation path and sales motion; flag early blockers.
|
||
-- Evidence: Commercial go/concerns note
|
||
-- Failure modes: Commercial viability ignored
|
||
|
||
-- G1 | Acct/Sales
|
||
-- Instructions: Confirm client demand/target clients; confirm client sign-off path; capture constraints/commitments.
|
||
-- Evidence: Account context note
|
||
-- Failure modes: Client expectations set without governance
|
||
|
||
-- G1 | Compliance
|
||
-- Instructions: Review intended boundaries; flag any prohibited uses early.
|
||
-- Evidence: Compliance boundary review note
|
||
-- Failure modes: Compliance issues found late
|
||
|
||
-- G1 | Legal
|
||
-- Instructions: Light-touch check on boundaries/disclaimers direction; confirm likely waiver/MSA needs.
|
||
-- Evidence: Legal boundary review note
|
||
-- Failure modes: Terms/disclaimers delayed
|
||
|
||
-- G2 | Product
|
||
-- Instructions: Ensure sizing + prioritisation completed; confirm impacted stakeholders aligned; record priority decision.
|
||
-- Evidence: Prioritised backlog record + rationale
|
||
-- Failure modes: G2 exit criteria missing; disagreement on priority; hidden dependencies
|
||
|
||
-- G2 | Product
|
||
-- Instructions: Create sizing tickets (epic + key work items); run RICE/BFC; schedule stakeholder review.
|
||
-- Evidence: JIRA/Planner items; RICE/BFC scoring sheet
|
||
-- Failure modes: Sizing skipped; cannot plan delivery
|
||
|
||
-- G2 | Tech Lead
|
||
-- Instructions: Provide effort range + dependencies; estimate major risks; contribute to cost-of-run.
|
||
-- Evidence: Estimate + dependency list
|
||
-- Failure modes: Under/over estimation; missing integration work
|
||
|
||
-- G2 | Finance
|
||
-- Instructions: Validate unit economics v0 (cost-of-run); flag margin risk; suggest thresholds for IB-like cost controls if needed.
|
||
-- Evidence: Cost-of-run estimate record
|
||
-- Failure modes: Cost ignored; later burn-rate issues
|
||
|
||
-- G2 | Commericial
|
||
-- Instructions: Check pricing hypothesis can cover cost-of-run; flag if it can’t.
|
||
-- Evidence: Viability note
|
||
-- Failure modes: Loss-making agent built
|
||
|
||
-- G2 | Client services
|
||
-- Instructions: Confirm downstream operational impact and sequencing constraints.
|
||
-- Evidence: Ops impact note
|
||
-- Failure modes: Launch blocked by ops capacity
|
||
|
||
-- G2 | Support
|
||
-- Instructions: Confirm support impact and capacity assumptions.
|
||
-- Evidence: Support impact note
|
||
-- Failure modes: Support not ready later
|
||
|
||
-- G2 | Sponsor
|
||
-- Instructions: Confirm priority aligns to business goals.
|
||
-- Evidence: Sponsor acknowledgement
|
||
-- Failure modes: Stakeholder misalignment
|
||
|
||
-- G2 | Exec/Gov
|
||
-- Instructions: Resolve cross-portfolio conflicts; approve if Change Board governance required.
|
||
-- Evidence: Change Board decision record
|
||
-- Failure modes: No governance path for conflicts
|
||
|
||
-- G3 | Product
|
||
-- Instructions: Own concept completeness; coordinate reviews; ensure all required sign-offs obtained.
|
||
-- Evidence: Concept pack link; G3 approval record
|
||
-- Failure modes: Missing key sign-offs; concept too vague
|
||
|
||
-- G3 | Product
|
||
-- Instructions: Define capabilities/boundaries; support/training needs; documentation requirements; consolidate concept pack.
|
||
-- Evidence: Capabilities/boundaries doc; support/training notes; doc checklist
|
||
-- Failure modes: Scope creep; no support plan
|
||
|
||
-- G3 | Tech Lead
|
||
-- Instructions: Define technical approach (high level); constraints; monitoring approach; feasibility refinements.
|
||
-- Evidence: Technical concept summary
|
||
-- Failure modes: Technical risks discovered too late
|
||
|
||
-- G3 | Compliance
|
||
-- Instructions: Define safety controls (guardrails, escalation/handoff); define data handling rules; define evaluation expectations.
|
||
-- Evidence: Safety controls spec; data handling plan; compliance sign-off
|
||
-- Failure modes: Safety not designed; data use not compliant
|
||
|
||
-- G3 | QA
|
||
-- Instructions: Create evaluation plan + test set + pass/fail thresholds (or assign evaluator).
|
||
-- Evidence: Eval plan + test set link
|
||
-- Failure modes: No measurable quality bar
|
||
|
||
-- G3 | Legal
|
||
-- Instructions: Confirm waiver/MSA/terms/disclaimer needs; agree liability/support stance direction.
|
||
-- Evidence: Legal concept approval note
|
||
-- Failure modes: Liability unclear; terms not ready
|
||
|
||
-- G3 | Commericial
|
||
-- Instructions: Create PPPP draft; confirm offer shape; coordinate early enablement needs.
|
||
-- Evidence: PPPP draft doc
|
||
-- Failure modes: No packaging/pricing clarity
|
||
|
||
-- G3 | Finance
|
||
-- Instructions: Review unit economics and implications for pricing/billing; confirm cost governance assumptions.
|
||
-- Evidence: Finance review note
|
||
-- Failure modes: Margin not understood
|
||
|
||
-- G3 | Client services
|
||
-- Instructions: Validate implementation approach and training needs; confirm feasibility.
|
||
-- Evidence: CS review note
|
||
-- Failure modes: Implementation not feasible at launch
|
||
|
||
-- G3 | Support
|
||
-- Instructions: Validate support stance/escalation; confirm support feasibility.
|
||
-- Evidence: Support review note
|
||
-- Failure modes: Support model rejected late
|
||
|
||
-- G3 | Acct/Sales
|
||
-- Instructions: Confirm client constraints, pilot candidates, and acceptance/sign-off approach.
|
||
-- Evidence: Account review note
|
||
-- Failure modes: Client not aligned
|
||
|
||
-- G3 | Marketing
|
||
-- Instructions: Provide input on positioning/proposition (for PPPP).
|
||
-- Evidence: Marketing input note
|
||
-- Failure modes: Marketing added too late
|
||
|
||
-- G4 | Tech Lead
|
||
-- Instructions: Own build-ready design; ensure tickets build-ready; ensure versioning/material-change policy defined; ensure monitoring is implementable.
|
||
-- Evidence: Design doc/ADR links; ticket set; versioning policy
|
||
-- Failure modes: Late design churn; no change policy
|
||
|
||
-- G4 | Tech Lead
|
||
-- Instructions: Drive design sessions; confirm permissions model; confirm monitoring instrumentation plan.
|
||
-- Evidence: Design notes and decisions
|
||
-- Failure modes: Permissions or monitoring missing
|
||
|
||
-- G4 | Architecture
|
||
-- Instructions: Produce/approve architecture decisions (ADR), integrations, patterns.
|
||
-- Evidence: ADR(s) + architecture sign-off
|
||
-- Failure modes: Architecture not captured; rework later
|
||
|
||
-- G4 | Security/IT
|
||
-- Instructions: Approve connectors/permissions/secrets/access controls; approve security readiness.
|
||
-- Evidence: Security sign-off + connector approvals
|
||
-- Failure modes: Excess privilege; connector approvals missing
|
||
|
||
-- G4 | Compliance
|
||
-- Instructions: Confirm monitoring covers safety events; confirm policy alignment; confirm change triggers.
|
||
-- Evidence: Compliance design sign-off
|
||
-- Failure modes: Safety monitoring missing
|
||
|
||
-- G4 | Legal
|
||
-- Instructions: Finalise waiver/MSA/contract needs and confirm path to readiness.
|
||
-- Evidence: Waiver/MSA status record
|
||
-- Failure modes: Contract readiness delayed
|
||
|
||
-- G4 | Deployment
|
||
-- Instructions: Validate deploy/rollback feasibility and environment needs early.
|
||
-- Evidence: Deployment feasibility note
|
||
-- Failure modes: Deployment issues discovered late
|
||
|
||
-- G4 | DevOps
|
||
-- Instructions: Confirm RC tagging/build approach and rollback mechanisms.
|
||
-- Evidence: DevOps note
|
||
-- Failure modes: No reproducible RC process
|
||
|
||
-- G4 | Product
|
||
-- Instructions: Confirm scope, acceptance criteria, and stakeholder alignment.
|
||
-- Evidence: Product design acceptance note
|
||
-- Failure modes: Requirements unclear
|
||
|
||
-- G5 | Tech Lead
|
||
-- Instructions: Coordinate build; ensure RC tagged; ensure test evidence exists; manage known issues and disposition.
|
||
-- Evidence: RC tag/build link; test report links; known issues log
|
||
-- Failure modes: Missing evidence; RC unclear
|
||
|
||
-- G5 | Engineer
|
||
-- Instructions: Implement agent per design; instrument logs/metrics; fix defects.
|
||
-- Evidence: Code/config/agent changes
|
||
-- Failure modes: Uninstrumented agent; recurring defects
|
||
|
||
-- G5 | QA
|
||
-- Instructions: Run evaluation + safety tests; document pass/fail; retest after fixes.
|
||
-- Evidence: Evaluation report + results
|
||
-- Failure modes: No repeatable test evidence
|
||
|
||
-- G5 | DevOps
|
||
-- Instructions: Tag/build release candidate; ensure deployable artifact reproducible.
|
||
-- Evidence: RC tag/build artifact
|
||
-- Failure modes: Unable to reproduce what was tested
|
||
|
||
-- G5 | Compliance
|
||
-- Instructions: Review safety results; ensure misuse/adversarial coverage included; approve safety readiness.
|
||
-- Evidence: Compliance test sign-off
|
||
-- Failure modes: Misuse risk untested
|
||
|
||
-- G5 | Security/IT
|
||
-- Instructions: Review misuse findings and permissions; confirm no security blockers.
|
||
-- Evidence: Security test sign-off
|
||
-- Failure modes: Security issues found late
|
||
|
||
-- G5 | Finance
|
||
-- Instructions: Review cost burn test results; confirm within thresholds and alerting plan.
|
||
-- Evidence: Burn test report + finance approval
|
||
-- Failure modes: Burn exceeds budget; no thresholds
|
||
|
||
-- G5 | Product
|
||
-- Instructions: Accept known issues disposition; confirm release scope.
|
||
-- Evidence: Product acceptance note
|
||
-- Failure modes: Unknown issues shipped
|
||
|
||
-- G6 | Product
|
||
-- Instructions: Run launch readiness checklist; ensure all required sign-offs obtained; chair launch readiness approval.
|
||
-- Evidence: G6 checklist complete + approvals
|
||
-- Failure modes: Launch blocked by missing readiness
|
||
|
||
-- G6 | Deployment
|
||
-- Instructions: Produce deployment plan + rollback + kill switch; schedule change window; execute readiness drills if needed.
|
||
-- Evidence: Deployment runbook
|
||
-- Failure modes: Rollback not tested; no change window
|
||
|
||
-- G6 | Client services
|
||
-- Instructions: Produce hypercare plan; implementation readiness; client rollout plan; coordinate UAT/hypercare logistics.
|
||
-- Evidence: Hypercare plan; rollout plan
|
||
-- Failure modes: Hypercare undefined; ops capacity mismatch
|
||
|
||
-- G6 | Support
|
||
-- Instructions: Confirm support model/SLA; staffing; escalation; service desk readiness requirements.
|
||
-- Evidence: Support model/SLA sign-off
|
||
-- Failure modes: Support can’t staff SLA
|
||
|
||
-- G6 | Marketing
|
||
-- Instructions: Prepare comms plan and enablement assets required for sold offering.
|
||
-- Evidence: Comms/enablement pack
|
||
-- Failure modes: Inadequate enablement
|
||
|
||
-- G6 | Commericial
|
||
-- Instructions: Finalise PPPP; confirm offer readiness; align sales enablement.
|
||
-- Evidence: PPPP final + approval
|
||
-- Failure modes: Pricing/packaging not final
|
||
|
||
-- G6 | Finance
|
||
-- Instructions: Confirm billing readiness; validate billing workflows; confirm margin tracking approach.
|
||
-- Evidence: Billing sign-off
|
||
-- Failure modes: Billing not ready at go-live
|
||
|
||
-- G6 | Legal
|
||
-- Instructions: Provide final legal approval (waivers/terms/disclaimers) and confirm deploy/sell permitted.
|
||
-- Evidence: Legal sign-off
|
||
-- Failure modes: Terms not ready; waiver missing
|
||
|
||
-- G6 | Procurement
|
||
-- Instructions: Ensure contract storage + renewal reminders configured (group-owned, not个人).
|
||
-- Evidence: Repo link + reminder confirmation
|
||
-- Failure modes: Auto-renew surprises
|
||
|
||
-- G6 | Compliance
|
||
-- Instructions: Confirm data/safety controls ready; confirm monitoring/alerting aligned to policy.
|
||
-- Evidence: Compliance launch sign-off
|
||
-- Failure modes: Compliance finds blockers late
|
||
|
||
-- G6 | Security/IT
|
||
-- Instructions: Confirm access, secrets, connector controls, monitoring/alerts readiness.
|
||
-- Evidence: Security launch sign-off
|
||
-- Failure modes: Security concerns late
|
||
|
||
-- G6 | Tech Lead
|
||
-- Instructions: Confirm technical readiness and supportability; confirm monitoring live.
|
||
-- Evidence: TL readiness note
|
||
-- Failure modes: Tech readiness assumed
|
||
|
||
-- G6 | Acct/Sales
|
||
-- Instructions: Confirm external comms, client rollout, and client expectations.
|
||
-- Evidence: Account readiness note
|
||
-- Failure modes: Client not briefed
|
||
|
||
-- G6 | Sponsor
|
||
-- Instructions: Final business confirmation; accept risks/conditions.
|
||
-- Evidence: Sponsor approval record
|
||
-- Failure modes: No executive backing
|
||
|
||
-- G7 | Support
|
||
-- Instructions: Accept ownership; confirm escalation paths; ensure service desk routing configured and working.
|
||
-- Evidence: Support acceptance sign-off
|
||
-- Failure modes: Service desk not configured
|
||
|
||
-- G7 | Client services
|
||
-- Instructions: Coordinate handover sessions; validate readiness against rollout plans.
|
||
-- Evidence: Handover notes
|
||
-- Failure modes: Handover incomplete
|
||
|
||
-- G7 | Tech Lead
|
||
-- Instructions: Deliver runbook/support notes; walk through known issues; provide troubleshooting guidance.
|
||
-- Evidence: Runbook link; troubleshooting notes
|
||
-- Failure modes: Runbook missing or outdated
|
||
|
||
-- G7 | Deployment
|
||
-- Instructions: Confirm operational deployment procedures are understood by support/CS.
|
||
-- Evidence: Deployment handover note
|
||
-- Failure modes: Deployment knowledge silo
|
||
|
||
-- G7 | DevOps
|
||
-- Instructions: Confirm RC/version references are clear for support; assist with operational tooling.
|
||
-- Evidence: DevOps handover note
|
||
-- Failure modes: Support can’t identify versions
|
||
|
||
-- G7 | Security/IT
|
||
-- Instructions: Confirm access procedures documented and least-privilege applied.
|
||
-- Evidence: Access/control confirmation
|
||
-- Failure modes: Support lacks access or has too much
|
||
|
||
-- G8 | QA
|
||
-- Instructions: Run staging smoke/regression; verify monitoring works; manage retest cycles.
|
||
-- Evidence: Staging test evidence
|
||
-- Failure modes: Staging unstable; monitoring not verified
|
||
|
||
-- G8 | Deployment
|
||
-- Instructions: Deploy to staging; maintain environment stability.
|
||
-- Evidence: Staging deployment record
|
||
-- Failure modes: Environment issues block testing
|
||
|
||
-- G8 | Tech Lead
|
||
-- Instructions: Support fixes, configuration, and stability; coordinate defect resolution.
|
||
-- Evidence: Defect log + fixes
|
||
-- Failure modes: Defects linger; no ownership
|
||
|
||
-- G8 | Engineer
|
||
-- Instructions: Fix defects discovered in staging and support retesting.
|
||
-- Evidence: Fix evidence
|
||
-- Failure modes: Re-test not done
|
||
|
||
-- G9 | UAT owner
|
||
-- Instructions: Execute UAT plan; confirm acceptance/rejection; ensure evidence captured.
|
||
-- Evidence: UAT completion record
|
||
-- Failure modes: UAT incomplete; no evidence
|
||
|
||
-- G9 | Client services
|
||
-- Instructions: Coordinate UAT scripts, participants, timing; manage feedback and retest loop.
|
||
-- Evidence: UAT coordination notes
|
||
-- Failure modes: UAT poorly run
|
||
|
||
-- G9 | Product
|
||
-- Instructions: Track UAT outcomes; decide on scope of fixes; confirm readiness to proceed.
|
||
-- Evidence: UAT decision log
|
||
-- Failure modes: Scope confusion
|
||
|
||
-- G9 | Acct/Sales
|
||
-- Instructions: Obtain client sign-off and manage client communications.
|
||
-- Evidence: Client sign-off evidence
|
||
-- Failure modes: Client sign-off missing
|
||
|
||
-- G9 | Legal
|
||
-- Instructions: Verify disclaimers/terms are correct in experience; confirm client-facing legal readiness.
|
||
-- Evidence: Legal verification record
|
||
-- Failure modes: Wrong disclosures shown
|
||
|
||
-- G9 | Compliance
|
||
-- Instructions: Verify compliance-sensitive behavior and disclosures; confirm acceptable use.
|
||
-- Evidence: Compliance verification record
|
||
-- Failure modes: Policy breach discovered late
|
||
|
||
-- G9 | Tech Lead
|
||
-- Instructions: Provide fixes/support for issues requiring code/config changes.
|
||
-- Evidence: Fix notes
|
||
-- Failure modes: Slow turnaround
|
||
|
||
-- G9 | QA
|
||
-- Instructions: Support retesting and validation of fixes.
|
||
-- Evidence: Retest evidence
|
||
-- Failure modes: No validation
|
||
|
||
-- G10 | Product
|
||
-- Instructions: Chair Go/No-Go; approve beta exit; approve GA acceptance decision.
|
||
-- Evidence: Go/No-Go record; beta exit decision record
|
||
-- Failure modes: No clear go/no-go authority
|
||
|
||
-- G10 | Deployment
|
||
-- Instructions: Deploy to live; execute rollback if needed; document deployment.
|
||
-- Evidence: Live deploy record
|
||
-- Failure modes: Rollback unprepared
|
||
|
||
-- G10 | Tech Lead
|
||
-- Instructions: Verify technical health; support incident response; confirm monitoring signals healthy.
|
||
-- Evidence: Production verification evidence
|
||
-- Failure modes: Live issues not detected
|
||
|
||
-- G10 | Support
|
||
-- Instructions: Monitor incidents and user issues during beta; run hypercare response.
|
||
-- Evidence: Beta monitoring report
|
||
-- Failure modes: Support overwhelmed
|
||
|
||
-- G10 | Client services
|
||
-- Instructions: Coordinate beta participants, comms, training, and feedback loops.
|
||
-- Evidence: Beta coordination notes
|
||
-- Failure modes: Beta unmanaged
|
||
|
||
-- G10 | QA
|
||
-- Instructions: Perform production smoke checks and verification.
|
||
-- Evidence: Smoke checklist evidence
|
||
-- Failure modes: No verification after deploy
|
||
|
||
-- G10 | Compliance
|
||
-- Instructions: Monitor safety incidents; confirm beta is within acceptable risk; approve beta exit conditions.
|
||
-- Evidence: Compliance beta sign-off
|
||
-- Failure modes: Safety incidents ignored
|
||
|
||
-- G10 | Legal
|
||
-- Instructions: Confirm no legal blockers; support incident communications; confirm terms/disclaimers remain correct.
|
||
-- Evidence: Legal beta sign-off
|
||
-- Failure modes: Legal risk escalates
|
||
|
||
-- G10 | Finance
|
||
-- Instructions: Confirm billing live; monitor spend during beta.
|
||
-- Evidence: Billing live confirmation; spend snapshot
|
||
-- Failure modes: Billing issues unnoticed
|
||
|
||
-- G10 | Commericial
|
||
-- Instructions: Confirm GA readiness for selling; align sales enablement timing.
|
||
-- Evidence: Commercial GA note
|
||
-- Failure modes: Sales starts before ready
|
||
|
||
-- G10 | Acct/Sales
|
||
-- Instructions: Manage client comms and expectations; coordinate client feedback.
|
||
-- Evidence: Client comms evidence
|
||
-- Failure modes: Client unhappy due to misalignment
|
||
|
||
-- G11 | Support
|
||
-- Instructions: Run hypercare; manage incidents; confirm stability; approve exit to BAU.
|
||
-- Evidence: Hypercare report + stability confirmation
|
||
-- Failure modes: Hypercare ends too early
|
||
|
||
-- G11 | Support
|
||
-- Instructions: Operate support processes; maintain ticket routing; escalate appropriately.
|
||
-- Evidence: Ticket metrics/records
|
||
-- Failure modes: Escalations unclear
|
||
|
||
-- G11 | Client services
|
||
-- Instructions: Support implementation/rollout follow-through; assist with adoption.
|
||
-- Evidence: Adoption notes
|
||
-- Failure modes: Adoption stalls
|
||
|
||
-- G11 | Product
|
||
-- Instructions: Track KPIs/adoption; prioritise improvements; decide keep/iterate/deprecate.
|
||
-- Evidence: KPI/adoption report
|
||
-- Failure modes: No outcome tracking
|
||
|
||
-- G11 | Finance
|
||
-- Instructions: Track cost vs budget + margin; report variances.
|
||
-- Evidence: Cost/margin report
|
||
-- Failure modes: Margin erosion unseen
|
||
|
||
-- G11 | Compliance
|
||
-- Instructions: Run quarterly recertification review (safety, data, changes).
|
||
-- Evidence: Recertification record
|
||
-- Failure modes: No recertification; drift risk
|
||
|
||
-- G11 | Security/IT
|
||
-- Instructions: Review permissions/connectors periodically; confirm no creep.
|
||
-- Evidence: Access review note
|
||
-- Failure modes: Permission creep
|
||
|
||
-- G11 | Legal
|
||
-- Instructions: Review if terms/disclaimers/contracts change or incidents require legal action.
|
||
-- Evidence: Legal review note
|
||
-- Failure modes: Terms outdated
|
||
|
||
-- G11 | Commericial
|
||
-- Instructions: Review commercial performance; adjust packaging/pricing if needed.
|
||
-- Evidence: Commercial performance note
|
||
-- Failure modes: Offer misfit persists
|
||
|
||
-- G11 | Sponsor
|
||
-- Instructions: Confirm outcomes acceptable; approve major changes or continued investment.
|
||
-- Evidence: Sponsor note
|
||
-- Failure modes: Sponsor disengaged
|
||
|
||
-- G12 | Product
|
||
-- Instructions: Own EOL decision; ensure closure across users/data/contracts; approve completion.
|
||
-- Evidence: EOL approval record
|
||
-- Failure modes: EOL incomplete; lingering risk/cost
|
||
|
||
-- G12 | Client services
|
||
-- Instructions: Plan and execute deprecation comms; coordinate offboarding; manage impact.
|
||
-- Evidence: Comms evidence; offboarding checklist
|
||
-- Failure modes: Users not migrated
|
||
|
||
-- G12 | Support
|
||
-- Instructions: Support offboarding and incident response during shutdown period.
|
||
-- Evidence: Support closure notes
|
||
-- Failure modes: Residual support burden
|
||
|
||
-- G12 | Security/IT
|
||
-- Instructions: Revoke permissions/connectors; decommission access; confirm shutdown controls.
|
||
-- Evidence: Access revocation evidence
|
||
-- Failure modes: Access left open
|
||
|
||
-- G12 | Compliance
|
||
-- Instructions: Confirm data cleaned/retention/disposal; confirm policy compliance.
|
||
-- Evidence: Compliance closure evidence
|
||
-- Failure modes: Data not disposed correctly
|
||
|
||
-- G12 | Finance
|
||
-- Instructions: Close billing; stop charges; confirm financials clean.
|
||
-- Evidence: Billing stop confirmation
|
||
-- Failure modes: Ongoing charges
|
||
|
||
-- G12 | Procurement
|
||
-- Instructions: Close contracts/serve notices; ensure no auto-renewal; store closure evidence.
|
||
-- Evidence: Contract closure evidence
|
||
-- Failure modes: Auto-renewal triggers
|
||
|
||
-- G12 | Legal
|
||
-- Instructions: Close legal obligations, notices, and client contractual requirements.
|
||
-- Evidence: Legal closure note
|
||
-- Failure modes: Client disputes
|
||
|
||
-- G12 | Acct/Sales
|
||
-- Instructions: Manage client comms and relationship during deprecation (if client-facing).
|
||
-- Evidence: Client comms evidence
|
||
-- Failure modes: Client dissatisfaction
|
||
|
||
-- G12 | DevOps
|
||
-- Instructions: Assist with decommissioning steps and archiving/version history.
|
||
-- Evidence: Decommission log
|
||
-- Failure modes: Decom missed steps
|
||
|