Roadmap & PoC Execution Planning: Sprint-Level Delivery Architecture

$ARGUMENTS format: [scope] [duration] [team-model]
Examples:
  "loan-origination PoC 4 weeks"           → scope=loan-origination, duration=4w, model=default
  "full MVP 8 weeks distributed team"       → scope=MVP, duration=8w, model=distributed
  "infrastructure migration 6 weeks"        → scope=infra, duration=6w, model=default

Read ${CLAUDE_SKILL_DIR}/references/roadmap-patterns.md

Week 0        Week 1-2        Week 3-4        Week 5+
PRE-SERVICE   SPRINT 1        SPRINT 2        STABILIZE
Kickoff       Foundation      Integration     Deploy

IF team size <4 engineers → extend sprints to 3 weeks (reduce meeting-to-coding ratio)
IF critical prerequisite blocked at Week 0 → escalate with quantified delay cost ("Team waiting costs $X/day")
IF Sprint 1 gate fails → execute remediation sprint before Sprint 2 (skipping compounds defects)
IF budget >$500K → add PMO oversight and formal change control board
IF engagement >8 weeks → add mid-engagement retrospective and scope revalidation

graph TD
    subgraph Core["Roadmap & PoC Core"]
        A[metodologia-roadmap-poc]
        A1[S1: Pre-Service Kickoff]
        A2[S2: Prerequisites Validation]
        A3[S3: Sprint Breakdown]
        A4[S4: Team & Budget]
        A5[S5: Timeline Visualization]
        A6[S6: Gate Criteria]
        A7[S7: Risk Register]
    end
    subgraph Inputs["Inputs"]
        I1[PoC/MVP Scope]
        I2[Duration Constraint]
        I3[Team Model]
        I4[Architecture/Design Phase Output]
    end
    subgraph Outputs["Outputs"]
        O1[Roadmap Document]
        O2[Gantt Chart]
        O3[Prerequisites Tracker]
        O4[Risk Register]
    end
    subgraph Related["Related Skills"]
        R1[metodologia-cost-estimation]
        R2[metodologia-commercial-model]
        R3[metodologia-solution-roadmap]
        R4[metodologia-discovery-handover]
    end
    I1 --> A
    I2 --> A
    I3 --> A
    I4 --> A
    A --> A1 --> A2 --> A3 --> A4 --> A5 --> A6 --> A7
    A --> O1
    A --> O2
    A --> O3
    A --> O4
    R1 --> A
    A --> R2
    R3 --- A
    A --> R4

# Roadmap & PoC — {proyecto}
## Resumen Ejecutivo
> Duracion: N semanas. Sprints: M. Team: X FTEs. Budget range: $Y +/-20%.
## S1: Pre-Service Kickoff (Week 0)
| Actividad | Owner | Duracion | Outcomes |
## S2: Prerequisites
| ID | Prerequisite | Status | Owner | Deadline | Blocker |
## S3: Sprint Breakdown
### Sprint 1 — [Target]
[Day-by-day plan with owners and deliverables]
## S4-S7: [secciones completas]
## Timeline
```mermaid
gantt
    title PoC Roadmap
    ...

**Formato HTML (para kickoff con cliente):**

### HTML (bajo demanda)
- Filename: `{fase}_roadmap_poc_{cliente}_{WIP}.html`
- Estructura: HTML self-contained branded (Design System MetodologIA v5). Timeline visual tipo Timeline con Gantt interactivo, prerequisites status board con semáforo, sprint accordion expandible y gate criteria checklist. WCAG AA, responsive, print-ready.

### DOCX (bajo demanda)
- Filename: `{fase}_roadmap_poc_{cliente}_{WIP}.docx`
- Generado via python-docx con MetodologIA Design System v5. Portada, TOC automático, encabezados en Poppins (navy), cuerpo en Montserrat, acentos en gold. Tablas de prerequisites, sprint breakdown y risk register con zebra striping. Encabezados y pies de página con branding MetodologIA.

### XLSX (bajo demanda)
- Filename: `{fase}_roadmap_poc_{cliente}_{WIP}.xlsx`
- Generado via openpyxl con MetodologIA Design System v5. Encabezados con fondo navy y texto Poppins blanco, cuerpo en Montserrat, zebra striping en filas. Hojas: Prerequisites Tracker (ID, prerequisito, status, owner, deadline, blocker flag), Sprint Breakdown (sprint, día, tarea, owner, entregable, acceptance criteria), Risk Register (ID, descripción, probabilidad, impacto, delay días, cost impact, mitigación, owner), Team & Budget (rol, tipo, FTE, fase). Conditional formatting por status de prerequisitos y severidad de riesgos. Auto-filters en todas las hojas. Valores directos sin fórmulas.

### PPTX (bajo demanda)
- Filename: `{fase}_roadmap_poc_{cliente}_{WIP}.pptx`
- Generado via python-pptx con MetodologIA Design System v5. Slide master con gradiente navy, títulos en Poppins, cuerpo en Montserrat, acentos en gold. Máx 20 slides ejecutivo / 30 técnico. Notas del presentador con referencias de evidencia. Slides: Pre-Service Kickoff Agenda, Prerequisites Status Board, Timeline Visualization (Gantt), Sprint Breakdown, Team Composition, Gate Criteria, Risk Register, Budget Summary.

## Evaluacion

| Dimension | Peso | Criterio | Umbral Minimo |
|-----------|------|----------|---------------|
| Trigger Accuracy | 10% | El skill se activa ante prompts de roadmap, PoC, sprint plan, execution timeline, milestones | 7/10 |
| Completeness | 25% | 9+ prerequisites con status y blocker flag; sprints con task allocation diaria; gates con criterios medibles; budget con breakdown y burn rate | 7/10 |
| Clarity | 20% | Timeline muestra 4+ milestones con critical path; el equipo puede ejecutar Day 1 sin retrabajo; gates son binarios | 7/10 |
| Robustness | 20% | Edge cases cubiertos (prerequisito bloqueado, equipo chico, gate fails, budget sin equipo); conditional logic documentada | 7/10 |
| Efficiency | 10% | Variante ejecutiva vs tecnica correctamente aplicada; duracion de kickoff adaptada al contexto (full vs lightweight) | 7/10 |
| Value Density | 15% | Risk register con 5-6 riesgos cuantificados (delay days + cost impact); cada entregable tiene acceptance criteria testeable | 7/10 |

**Umbral minimo global: 7/10.** Si alguna dimension cae por debajo, el entregable requiere revision antes de entrega.

## Cross-References

- **metodologia-cost-estimation:** Cost estimation that feeds budget ranges in the roadmap
- **metodologia-commercial-model:** Commercial model that uses roadmap for pricing and delivery terms
- **metodologia-solution-roadmap:** Strategic multi-year roadmap where PoC roadmap is a tactical slice
- **metodologia-discovery-handover:** Handover document that references roadmap for execution planning

## Output Format Protocol

| Format | Default | Description |
|--------|---------|-------------|
| `markdown` | Yes | Rich Markdown + Mermaid diagrams (Gantt). Token-efficient. |
| `html` | On demand | Branded HTML (Design System). Visual impact. |
| `dual` | On demand | Both formats. |

Default output is Markdown with embedded Mermaid Gantt diagrams. HTML generation requires explicit `{FORMATO}=html` parameter.

## Output Artifact

**Primary:** `RP-01_Roadmap_PoC_{project}.md` (or `.html` if `{FORMATO}=html|dual`) — Pre-service kickoff, prerequisites validation, sprint breakdown, team composition, budget range, timeline, gate criteria, risk register.

**Secondary:** Gantt chart (Mermaid), parallel setup grid, prerequisites tracker, risk register spreadsheet.

---
**Autor:** Javier Montaño | **Ultima actualizacion:** 12 de marzo de 2026