Capability Lifecycle — ODT Development Process

What It Is

SAFe is a framework for scaling Agile practices across large organizations. It synchronizes multiple teams around a shared mission through structured planning cycles called Program Increments (PIs) — typically 8-12 weeks of coordinated development.

Core Structure

• Program Increment (PI): A fixed timebox (~8-12 weeks) where teams plan, build, and deliver together
• PI Planning: A 2-day event where all teams align on objectives, dependencies, and risks
• Sprints: 2-week iterations within the PI (typically 4-5 per PI)
• Agile Release Train (ART): The team-of-teams that delivers value; led by a Release Train Engineer

Key Ceremonies

• PI Planning: All teams, face-to-face, plan the increment
• Scrum of Scrums: Cross-team sync on process, not content
• System Demo: Integrated demo at end of each sprint
• Inspect & Adapt: PI-level retrospective — what worked, what didn't, what to change

Key Roles

• Product Manager: Owns the "what" — priorities and requirements
• Scrum Master: Owns the "how" — facilitates the team, removes blockers
• Release Train Engineer (RTE): Facilitates the ART, coordinates across teams
• Business Owners: Stakeholders accountable for business outcomes

Principles

• Align strategy and execution through cadence-based planning
• Build incrementally with fast, integrated learning cycles
• Decentralize decisions to the teams closest to the work
• Reduce batch size — deliver smaller pieces more frequently

Common Pitfalls

• Over-ceremonializing — too many meetings defeats the purpose
• Treating PI Planning as a briefing instead of a working session
• Letting stakeholders bypass the ART and task developers directly
• Not protecting sprint time from ad-hoc requirements

What It Is

The Capability Lifecycle describes how a data capability moves from initial intake through fielding, sustainment, and eventual retirement. It is the end-to-end process that governs how the ODT identifies, builds, deploys, and evolves capabilities for the command.

The Five Phases

• Intake & Scoping: Hermes submission. Idea intake, initial scoping, and feasibility check determine whether the capability warrants further investment.
• Concept: Problem definition, initial planning, resource approval. Ends at the Approval Gate (PSB).
• Development (SAFe): Design & build via the Agile Release Train (ART). Process development, testing & validation. New capabilities built inside SAFe.
• Execution & Sustainment: Deploy capability, training & operations, ongoing support. Operationalized outside SAFe. Ends at the Transition Gate.
• Evolution / EOL: Evolve and upgrade the capability, or retire & decommission when no longer needed.

Decision Gates

Three decision points control progression. The Approval Gate (PSB with CG) authorizes transition from Concept to Development. The Demo/Retro Decision Gate (ART recommends, DSD Director signs off) is iterative — at the end of each PI, a product may invest (continue development), divest (discontinue), or pivot (change direction). Projects can cycle between Development and this gate multiple times, and may also cycle back to Concept if needed. The Transition Gate authorizes handoff from Execution & Sustainment to Evolution or EOL. No automatic advancement — each gate is a deliberate command decision.

SAFe Development vs. Operational Sustainment

New capabilities are built inside SAFe sprints with ART oversight. Once deployed, they are operationalized outside SAFe — sustained by operational teams, not developers. This distinction is critical: development capacity must be protected from sustainment drag.

Why This Matters

• Prevents building before understanding — Concept must clear the Approval Gate before development starts
• Forces resource allocation decisions — each phase requires different people and skills
• Creates accountability — CG-chaired PSB owns the Approval Gate
• Separates build from sustain — developers build, operational teams sustain

Evolution & EOL Reality

• Capabilities that are not formally evolved or retired create technical debt and operational risk
• Evolution (capability upgrades) cycles back through the Approval Gate for new development
• EOL is a deliberate act — retire & decommission with data archival and user migration
• Sustainment requires dedicated personnel — not the same team that built it