Devops in an Industrial Company: From Milestones to a Continuous Quality Assurance Approach
summary
Claims that continuous deployment in industrial products needs a parallel pipeline for non‑software artifacts and shows a working implementation: continuous conformance tied into toolchains, micro checklists and dashboards. Integrations presented include IBM Rational Team Concert, Jira and plans for Azure DevOps. Empirical result: only ~10–20% of changes require non‑software updates; artifacts fall into four types with differing lead times, so the process shifts left and enforces stricter “ready to develop” gates per backlog item.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 4:11Continuous Delivery Continuous Deployment
- 6:37Devops Target Scenario
- 9:41Continuous Quality Assurance Approach
- 10:24Continuous Integration
- 14:41Continuous Deployment
- 16:42Implementation
- 19:19Nonsoftware artifacts
- 24:55Feasibility study
- 27:26Continuous conformance management
- 34:35Key Idea
- 36:00Conclusion
related talks
15mDevOps - Future of IT
01h 01mA team's transition to Continuous Delivery
51mBetter software, faster: principles of Continuous Delivery and DevOps
34mDevOps: Next
31mThe Continuous Culture
25mDevOps Bringing a New Concept to Software Quality
20mEnsuring Quality in DevOps Culture
34mYou only have to change one thing to do the DevOps