Migrate from Scrum to ForgeSDLC

Start with the comparison: ForgeSDLC vs Scrum — ceremony mapping, roles, artifacts, and cadence at a glance.

This page is the operational kit: how to run Forge as an overlay first, not a big-bang replacement. Context matrix: Forge vs traditional methodologies.

Principles

Keep Sprint length and predictability while you learn Forge vocabulary and evidence habits
Daily Scrum → Forge daily sync — same inspect/adapt intent: Charge, blockers, decisions needed; add Versona sessions or decision huddles as follow-ups when a discipline decision is required—not instead of the sync (meetings model)
One work hierarchy — user stories and tasks stay your WBS; Sparks map 1:1 to tasks; you are not running two backlogs
Charge is a view on today’s committed Sparks—many teams keep Jira/Azure DevOps and add Charge as how they talk about focus and risk

Week 0–1

Add the Blueprints submodule and pin SDLC plus one or two discipline blueprints (adoption playbook)
Agree naming for Ore/Ingot/Spark in your tracker (naming reference)
Train the team: hats, intent before execution, when to invoke a Versona vs a generic discussion

Sprint planning overlay

Treat planning as alignment + commitment to the iteration’s Sparks
Pull discipline checks from Blueprints when the backlog item implies risk (security, data, architecture)—optional Versona spike before committing heavy Sparks

Daily flow

Confirm Charge — what is actively in motion; what is blocked and who owns the next decision
Escalate to a Versona only when the blueprint says “this decision needs discipline X”

Review and release

Sprint Review maps to inspection of the increment; add Assay Gate thinking where you need explicit release evidence (criteria, tests, notes)—see Forge ceremonies
Retro stays short and actionable; milestone reviews when warranted (meetings model)

What not to do on day one

Do not mandate replacing your board with a new tool
Do not schedule Versona sessions instead of the daily sync for routine updates
Do not relabel every ceremony before behaviors (intent, logging, evidence) exist

Next: Sponsors hub · Adoption playbook