We continue our series responding to Martin Fowler's State of Agile 2018 speech. This week we look at Fowler's second claim - that agile software development has forgotten that it's about software, and that technical excellence in practises like refactoring, testing, and architecting should be (but isn't) central to discussions of good agile practise. We agree with Fowler and go even further, arguing that we should be making the (strong) case for technical excellence as a source of business value - to make our products more flexible, easier to use, and more satisfying to users.

SHOW LINKS:

- Fowler on the State of Agile 2018: https://martinfowler.com/articles/agile-aus-2018.html

- Marick on forgotten agile ideas: http://www.exampler.com/discipline-and-skill.html and http://www.exampler.com/blog/2007/05/16/six-years-later-what-the-agile-manifesto-left-out/

- Reinertsen, The Principles of Product Development Flow (cost of delay): https://www.amazon.co.uk/Principles-Product-Development-Flow-Generation/dp/1935401009

- Accelerate book: https://itrevolution.com/book/accelerate/

- Our previous episode on technical excellence and the agile principles: https://soundcloud.com/troubleshootingagile/enhancing-agility-through-technical-excellence-and-good-design

***

We'd love to hear any thoughts, ideas, or feedback you have about the show.

Email us: see link on troubleshootingagile.com

Tweet us: twitter.com/TShootingAgile

Also, if you'd like to leave us a review on iTunes (or just like and subscribe), you'll find us here: https://itunes.apple.com/gb/podcast/troubleshooting-agile/id1327456890?mt=2

Fowler's State of Agile - Part Two

Troubleshooting Agile is a problem-solving session for agile teams. Jeffrey Fredrick and Douglas Squirrel look at common problems agile teams face and provide practical, immediately useful advice for getting back on track.