Red Hat IT’s DevOps Journey: Year One Retrospective
summary
Two-year dedicated team called Inception targets measurable outcomes: cut cycle time and double release frequency. Team chooses release automation first, partners with SSSE and PlatOps, and builds open source release tool winter noot; a July POC deploys SOA nodes to QA with no hands on keyboard. Successes include a repeatable automation pattern and public metrics, setbacks include program scheduling conflicts and slipping quarterly gains. Lessons: clarify mission early, start lower risk, keep a permanent owner for changes.
AI-written summary · about
chapters (9)
- 0:00Introduction to Red Hat IT
- 2:49The DevOps initiative
- 5:16Building the Inception team
- 7:05Defining the mission
- 8:52Strategy and assessment
- 12:51Execution and partnerships
- 17:55Challenges and roadblocks
- 21:46Personal growth and reflections
- 25:02Lessons learned and conclusion
related talks
22mCreating a team mindset of continuous improvement
23mProduct & Project Manager’s DevOps Journey to Continuous Delivery
05mReady, Set, DevOps Roadblock
36mDevOpsSup - Extended DevOps approach
30mColumbia Sportswear Experience Report
25mDevOps Handbook Experiments in Accelerating Delivery
47mWhere the Security Rubber Meets the DevOps Road
22mA Healthier Software Development Life Cycle with DevOps