Holidays & Happy Hour:...
summary
USCIS’s Delivery Assurance Branch ties IV&V to concrete signals: pipelines move from 180‑day releases to daily deployments, CI/CD with Jenkins plus Docker and AWS supports blue‑green releases, and a microservice strategy replaces duplicated code. Measured outcomes include increased holiday and pre‑4pm deploys, non‑disruptive releases up while disruptive ones fall, and surprisingly high peer review — about 96% pull requests commented — which correlates with fewer escaped defects and steadier ops.
AI-written summary · about
chapters (24)
- 0:00Start
- 1:32OUR STORY: USCIS DOING AUDITABLE AGILE
- 1:57RESULTS AT USCIS. Software Delivery Times Drastically Reduced
- 6:21WHERE WE ARE NOW
- 9:15OIT DELIVERY ASSURANCE BRANCH
- 9:46PROVIDING EVIDENCE TO AUDITORS
- 11:45HONORING THE SOCIAL CONTRACT
- 12:17USCIS BIGGEST SYSTEM
- 14:26MEASURING QUALITY
- 17:18FEAR, UNCERTAINTY, DOUBT
- 18:33METRICS NEED TO BE EASY
- 19:00WHAT TO MEASURE?
- 20:09MORE SOPHISTICATED & OBVIOUS SIGNS
- 20:48OUR GOAL IS TO CATCH DYSFUNCTION EARLY!
- 21:17IS DEPLOYING LIKE PUTTING ON SOCKS?
- 22:01OF WORK DAYS WITH A DEPLOYMENT
- 24:46CAN USERS KEEP WORKING?
- 25:49CAN WE CELEBRATE HOLIDAYS AND STILL DEPLOY?
- 28:33PULL REQUESTS WITH PEER REVIEW
- 29:05HELP DESK & USERS
- 29:57HOW MANY PEOPLE ARE CALLING HELP DESK
- 30:25STABLE USER-BASE
- 31:11ASK PEOPLE SIMPLE QUESTIONS
- 32:11RECAP
related talks
29mDOES14 - Mark Schwartz - U.S. Citizenship and Immigration Services
38mHow to stop worring about application Container security
51mBetter software, faster: principles of Continuous Delivery and DevOps
40mSustainable Continuous Delivery: Patterns for rapid and reliable Releases
30mContinuous Integration at Haptik : Our Journey to Hourly Releases
26mHuman Trust in Continuos Deployment
33mCI/CD for Autonomous Drive and other complex systems - What we have learned about...
01h 01mA team's transition to Continuous Delivery
