Episode 543: Jon Smart on Patterns and Anti-Patterns for Successful Software Delivery in Enterprises

Topics covered
Popular Clips
Episode Highlights
System Entropy
System entropy is a critical concept in understanding the degradation of both human and technical systems over time. explains that as systems age, they accumulate technical debt and bureaucratic processes, leading to inefficiencies and slower progress. He emphasizes the importance of continuous improvement in technology and processes to combat this entropy, advocating for a focus on technical excellence and regular refactoring 1.
Improving daily work is as important as daily work, and not doing that, you end up with the go slow to go faster, or you will end up going slower.
---
This approach, he notes, is essential to maintain agility and prevent the pitfalls of the anti-pattern "go faster to go slower."
Technical Excellence
Achieving technical excellence requires specific metrics and practices that focus on delivering value efficiently. highlights key measures such as time to value, lead time, flow efficiency, and quality, which he defines as the absence of unplanned work or failure demand 2. Safety and happiness are also crucial metrics, with safety encompassing data security and privacy, and happiness reflecting the satisfaction of both colleagues and customers.
Time to value, lead time and flow, efficiency, quality, safety and happiness, all of which leads to business value.
---
These metrics collectively contribute to business value, ensuring that technical excellence is not just about speed but also about sustainable and secure practices.
Evergreening
Evergreening is a vital practice to keep technology up-to-date and reduce technical debt. shares examples of organizations that failed to prioritize evergreening, resulting in outdated and unsupported software that hindered business operations 3. This neglect can lead to significant challenges, such as the inability to upgrade systems, forcing costly and risky overhauls.
It forces you into a corner where the only thing you can do is slash and burn and rewrite or roll out a new system, which is also not a good idea.
---
By maintaining an evergreen approach, businesses can enhance their agility and capacity to deliver value efficiently.
Related Episodes


Episode 457: Jeffery D Smith on DevOps Anti Patterns
Answers 383 questions

Episode 47: Interview Grady Booch
Answers 383 questionsEpisode 1: Patterns
Answers 383 questions
Episode 103: 10 years of Agile Experiences
Answers 383 questions
Episode 54: Interview Frank Buschmann
Answers 383 questions

Episode 188: Requirements in Agile Projects
Answers 383 questions

Episode 180: Leading Agile Developers with Jurgen Appelo
Answers 383 questions

Episode 441 Shipping Software - With Bugs
Answers 383 questions

Episode 76: Special Episode on the Patterns Journal
Answers 383 questions

Episode 6: Model-Driven Software Development Pt. 2
Answers 383 questions

Episode 190: Lean (Software) Development
Answers 383 questions

Episode 17: Feedback and Roadmap
Answers 383 questions
Episode 41: Architecture Patterns (Architecture Pt. 4)
Answers 383 questions
Episode 173: Feature-Oriented Software Development with Sven Apel – Pt 2
Answers 383 questions

Episode 112: Roles in Software Engineering II
Answers 383 questions













