Design after Agile: How to Succeed by Trying Less
summary
Argues that Agile needs stronger design heuristics and shows a concrete technique: make looser, composite diagrams instead of narrow UML slices. Uses the closure 1.10 prep 'el work as an example and describes diagrams that combine multiple UML views, mark subsystems and encapsulation boundaries, show captures time and information flow, note data formats and seams. Claims these artifacts cut misunderstanding during coding and remain useful five years later for maintenance.
AI-written summary · about
