Dan Ashby

Part 2 of 4: Rethinking the quality operating model for AI-native engineering I’ve seen and heard about how this has been playing out in different organisations, with different tools and different teams.

Part 1 of 4: Rethinking the quality operating model for AI-native engineering Here’s a scenario I’d suspect most engineering leaders reading this will recognise: An incident slips into production.

Part 4 in “The Autonomous Testing Tipping Point” series If you’ve been following along, you’ll know we’ve been exploring application integrity, the gap opening up between AI-accelerated development and our ability to test what we’re shipping, and the broa…

So… It’s here – the thing I’ve been hinting at across my past two articles.

Last week, in part 1, I set the scene: why testing is at a crossroads, what autonomous testing means as a spectrum (not a switch) across both teams and in AI systems, and how autonomy functions best.

I am increasingly getting the deep impression that software delivery teams are standing at a crossroads within the industry.

How good are the communities that you are part of?

In my last blog post, I shared my views on quality regarding goodness, value, and correctness.

What’s the quality of your product?

Philip Crosby has a big reputation as being a quality leader in the manufacturing industry, having authored many books on quality between 1968 and 1999.