Adoption for sponsors
ForgeSDLC is best introduced as a documentation-led, pilot-first operating model—not a ceremonial rebrand. This hub collects paths for executives, enterprise change managers, and teams migrating from familiar frameworks.
Start here
| Audience | Page |
|---|---|
| Executives and business owners | Executive adoption overview — why now, fit, outcomes, what stays the same, first 90 days |
| Enterprise change managers | Enterprise change management — rollout, pilots, coexistence, scorecard |
| Practitioners comparing frameworks | Forge vs traditional methodologies |
Migration kits (single-page)
Operational overlays: keep your existing cadence and tracker initially; add Forge mechanics around intent, Charge, Versonas, and repo evidence.
- Scrum → Forge — also see Forge vs Scrum
- Kanban → Forge — also see Forge vs Kanban
- Waterfall → Forge
- SAFe-adjacent → Forge
Traceability and governance
- Artifacts: before and after — how familiar items map to Forge vocabulary without a second taxonomy
- Governance and evidence pack — audit posture, architecture review, change control, coexistence with enterprise frameworks
- Adoption proof points — how pilot outcomes can be published (placeholder until case studies exist)
Operational depth
- Adoption playbook — week-by-week setup, Charge, first Versona session
- Scaling ForgeSDLC — multi-team patterns and portfolio visibility
Executive capsule
ForgeSDLC is best introduced as a documentation-led, pilot-first operating model—not a ceremonial rebrand. This hub collects paths for executives, enterprise change managers, and teams migrating from familiar frameworks. Maturity: defined.
Who this is for
Executives and sponsors at the adopt stage. Skim the executive capsule first; agents should respect the page frontmatter contract.
Evidence and maturity
Maturity: defined. Statements here reflect the owning repo (forgesdlc) at last_reviewed; treat anything not explicitly marked as demonstrated as design direction rather than a shipped guarantee.
Trust boundary
Forge keeps humans in charge of promotion, approval, and release decisions; automation proposes and executes only within approved boundaries described here.
How to use this page
Read top-to-bottom at your depth: capsule for the decision, mechanism for design, links below for the next step in your journey.
How it works
The sections above and below describe the mechanism in practice; read them top-to-bottom for the operating model, and follow the linked canonical references for contract-level detail.
Related
See the owning repo's documentation index for neighboring pages.