Evolutionary Software Quality
summary
Combines ISO 25010 and Wardley mapping to map specific quality attributes to evolution stages so architects know what to invest in when: genesis emphasizes functional suitability, custom‑build shifts to usability and performance, product requires security and maintainability, commodity stresses compatibility and portability. Uses Wardley-style value chains and empirical workshop data to show which qualities are visible to users versus developers, flags over‑engineering (e.g., building clean architecture before product‑market fit) and underinvestment (startup anecdote where technical focus kills adoption), and provides concrete prioritization guidance.
AI-written summary · about
chapters (15)
- 0:00Introduction to talk
- 1:16Defining software quality
- 3:48Evolutionary thinking approach
- 8:28Genesis phase quality needs
- 10:37Custom build phase priorities
- 13:04Product phase quality focus
- 16:45Commodity phase requirements
- 18:09Using the model for communication
- 21:07Startup failure lessons
- 22:35Prioritizing quality goals
- 24:02Value chain and stakeholder perspectives
- 27:10External vs internal qualities
- 30:22Team alignment challenges
- 32:32Model limitations and usefulness
- 33:21Q&A session
related talks
35mPrinciples of Evolutionary Architecture
01h 03mEvolutionary Software Architectures
42mBuilding Evolutionary Architectures: Principles and Practices
49mThe Principles of Evolutionary Architecture
39mPrinciples of Evolutionary Architecture
53mEvolutionary Architecture: Principles and Patterns
39mHow will Evolutionary Architecture evolve?
48mAgile is a cult