Case Study – Leonel Garciga
summary
JIDO shifts from six releases a year to 60 releases in 90 days by building a DevOps pipeline that ties requirements straight to operators and reduces deploy time to six-hour deploy from theater for combat fixes. Governance and RMF controls become more visible to the AO via a single-pane dashboard integrating Docker, Twistlock, and lightweight images like Alpine. Transformation takes about 24–48 months with roughly a 30% workforce reskill or redeploy and requires contract SLAs that enable continuous delivery and triaged risk thresholds.
AI-written summary · about
chapters (11)
- 0:00DevOps transformation
- 1:34The importance of ecosystem
- 4:20Process and tools
- 6:12Governance and risk
- 8:15Cultural challenges
- 10:49Human capital and security
- 12:41SLA and contracting
- 14:28Workforce transformation
- 17:04Lessons from industry
- 20:12Addressing critical questions
- 23:36Implementation timeline
related talks
26mDevOps and Lean in Legacy Environments
53mThe Road to Continuous Deployment: a Case Study
57mA continuous fairytale
05mRelease management as a catalyst for CI/CD
01h 01mA team's transition to Continuous Delivery
12mContinuous Deployment in a heavily regulated environment
33mUnleashing the Gorillacorn - DevOps in Very Large Enterprises
34mEnabling a Continuous Deployment Mindset