Agile needs systems thinking
summary
Argues that Agile teams must stop focusing only on code and become systems engineering organizations that design for high security, high usability, low technical debt. Calls for explicit design of data, machines, people, laws and cultures — data machines people laws cultures — with architects and engineers specifying nonfunctional requirements and tradeoffs. Warns current practice leaves programmers acting like hobby builders trying to erect a 300‑storey skyscraper without engineering controls.
AI-written summary · about
related talks
01h 09mAgile Software Architecture
49mAgile and Architecture: a meeting of the undead
41mAgile and Architecture: a meeting of the undead
01h 03mAgile Software Architecture
51mWhy We Need Architects (and Architecture) on Agile Projects
47mAgile and Architecture: a meeting of the undead
02mDesign after Agile: How to Succeed by Trying Less
53mAgile and Architecture: a meeting of the undead