Quality versus Agility: a conflict of interest?
summary
Argues that agility is itself a system quality and insists on making qualities explicit as quality metrics such as availability percentiles and MTTR, uses SEI design tactics and production monitoring to decide just-in-time architecture changes, shows a desk study where applying three decoupling tactics raises availability from 99.3 to 99.6, recommends putting quality work into the backlog as quality stories, demoing tactics (kill a node to prove redundancy) and using definition of done checks.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:10Meet Ada Paul
- 3:02Agile Architecture
- 4:27What is Architecture
- 6:55What is Agility
- 8:25Agility and Architecture
- 10:48NG Architecture
- 12:23Quality
- 14:34Quality serves a purpose
- 15:44Quality has metrics
- 17:32Quality can be specified
- 20:16How to design quality
- 21:21Availability
- 23:28Quality vs Agility
- 26:34Reporting for management
- 28:05Super duper agile
- 32:03Conclusion
related talks
46mAgility as a Quality of a Living System: Agility Enablement
36mSuddenly reality
36mFrom Software to Systems: Modern Agility
35mAgility and Architecture - Do Opposites Attract?
01h 22mAgile - The Road Towards Organizational Agility - Progress & Challenges Examined
40mBusiness Agility in practice with Integral Objectives
46mQuality Engineering for DevOps Teams
59mAgile Engineering: The Hard Parts