SAG Expert Interview #08: Fast Flow for agile & safe software deployment
summary
Argues that “fast flow” drives business agility by moving a continuous stream of changes from git push through an automated pipeline into production, enabling rapid experiments and feedback. Claims three essential elements: DevOps handbook practices, Team Topologies organizational patterns, and a change‑friendly architecture (modular monolith or microservices) chosen via explicit tradeoff analysis. Uses DORA metrics—notably deployment frequency >1 per developer/day, lead time ~15 minutes, low change‑failure rate and fast recovery—to prove high speed with high reliability.
AI-written summary · about
chapters (9)
- 0:00Start
- 0:18Introduction
- 0:59What is the concept of Fast Flow and why is it so helpful?
- 2:45What role does the strategic vision of an organisation play in this context?
- 3:33How can organisations put Fast Flow into practice?
- 6:10What skills and resources do software architects need to make use of Fast Flow?
- 8:43How can the success of Fast Flow integration be measured with DORA metrics?
- 9:35What is the situation regarding diversity awareness in these transition processes?
- 11:20How do you value conferences as a place to share experiences and knowledge?
related talks
48mAgility and Architecture Together – Enabling a Fast Flow of Change
23mThe Cost of Speed: Rethinking "Move Fast" in DevOps
01h 00mDevOps – Value at Speed
30mMoving Fast At Scale
54mGetting Unstuck. Strategies for Surviving in a Rapidly Changing Post-Agile World
18mDesign Patterns For Efficient DevOps Processes
28mPick any Three: Good, Fast, and Safe. DevOps from Scratch
29mEconomies of Speed