Story Map — Internal Developer Portal
Platform-team milestones along the service lifecycle — scaffold, ship, operate, comply — with bracketed estimates; the golden path gets an engineer to production before lunch but leaves every compliance control to the last milestone.
Make it your own.
title "Internal developer portal — platform roadmap"
persona "Backend engineer shipping their first service"
goal "Empty repository to production before lunch, without asking anyone"
release "M1 — Golden path"
release "M2 — Self-service"
release "M3 — Governance"
// The backbone follows the service lifecycle, not the team structure.
activity "Scaffold"
task "Create a service"
M1: "Template repository with CI already wired up" [8]
M2: "Templates for Go, Kotlin and Python" [13]
task "Register ownership"
M1: "Catalogue entry with an owning team" [5]
M3: "Ownership review when a team is dissolved" [8]
activity "Ship"
task "Build and test"
M1: "Pipeline that builds, tests and publishes an image" [13]
M2: "Preview environment per pull request" [13]
task "Deploy"
M1: "One-click deploy to staging and production" [13]
M2: "Progressive rollout with automatic rollback" [21]
later: "Deploy from the chat client" [8]
activity "Operate"
task "Observe"
M1: "Logs, metrics and traces linked from the catalogue" [8]
M2: "Service health scorecard on the team page" [8]
task "Respond"
M2: "On-call rota and escalation policy per service" [8]
M3: "Incident timeline assembled from deploys and alerts" [13]
activity "Comply"
task "Prove controls"
M3: "Evidence pack for change management" [13]
M3: "Dependency and licence inventory per service" [8]
task "Retire"
M3: "Decommission workflow with data disposal steps" [8]