Enabling technical agility in the Lean enterprise vlog series: building systems with design quality
We’re back with video 10 in our series designed to jump-start your understanding of the core principles and practices of Agile software engineering (ASE). This time, one of our Lean-Agile thought leaders, Ken Pugh, talks about aspects of design quality that are critical for maintainability.
Ken introduces Interface-Oriented Design by discussing one of the most important guiding principles—design to interfaces not implementations—from Design Patterns by Gamma et al. Next, he draws from another classic book in the field, Clean Code, by Bob Martin. Ken explains Martin’s five SOLID principles: Interface Separation, Dependency Inversion, the Liskov Substitution Principle, Single Responsibility, and Open/Closed, and what they mean for quality.
Watch here to soak up this wisdom and more, including what it means for an implementation to ‘do no harm.’
Check back next time for the video 11 in the series in which Ken will talk about implementing with quality.
Go here to see the previous video on another topic related to maintainability—building systems with code quality.
You can learn more about the Agile Software Engineering course here.