DOES14 - Mark Schwartz - U.S. Citizenship and Immigration Services
summary
Federal IT shifts from waterfall rules to automated pipelines: MD102 requires nine phases, 11 gate reviews and 90–110 documents per release, which forces eight‑month minimums; the alternative implements Jenkins, git, Chef, Gradle, New Relic and Amazon Cloud with automated tests for FISMA and Section 508, static analysis, and a continuous delivery pipeline that already handles ~75 legacy systems and ~100 agile releases while processing 7 million applications a year; experiments include a chaos monkey and metrics-driven cycle‑time reduction.
AI-written summary · about
chapters (7)
- 0:00Bureaucracy's bad rap
- 2:56First shock of bureaucracy
- 6:30Impossible 8-month cycle
- 11:15Human side of MD102
- 15:31Government low-trust environment
- 17:15DevOps meets government needs
- 26:36Cultural change foundations
related talks
33mHolidays & Happy Hour:...
38mHow to stop worring about application Container security
28mGrowing Pains - Scaling Jenkins in the Federal Sector
29mBusting Silos & Red Tape: DevOps in Federal Government
48mWhen DevOps Meets Regulation: Integrating 'Continuous' with 'Government'
57mA continuous fairytale
40mSecurity Automation in the agile SDLC - Real World Cases
51mTaking AppSec to 11: Pipelines, DevOps and making things better