Google’s DevOps Research and Assessment (DORA) team has spent over a decade studying what makes software teams perform at elite levels. Their latest evolution \u2014 the DORA AI Capabilities Model \u2014 expands the framework to account for artificial intelligence. But as many in the testing community are asking: if AI amplifies both the good and the bad in your delivery pipeline, where should your team actually start?<\/p>\n\n\n\n
The DORA Capabilities Model has long been the gold standard for measuring software delivery performance. It identifies specific technical and cultural practices that correlate with better outcomes \u2014 faster deployments, fewer failures, happier teams. The model groups capabilities into categories like continuous delivery, architecture, process, and cultural enablers.<\/p>\n\n\n\n
With the 2024\u20132025 update, DORA introduced a new layer: AI-specific capabilities<\/strong>. These aren’t standalone features you bolt onto an existing pipeline. Instead, they describe the conditions under which AI tools actually deliver on their promises \u2014 rather than creating new bottlenecks, security risks, or maintenance nightmares. The model now acknowledges what testers have been saying for years: garbage in, garbage out<\/em> applies to AI just as much as it does to manual processes.<\/p>\n\n\n\n DORA identifies four capabilities that specifically enable or constrain AI adoption in software delivery:<\/p>\n\n\n\n Here’s the critical insight from the model: the AI-specific capabilities only work when the foundational capabilities are already in place. You can’t have AI-accessible data if your documentation quality is poor. You can’t build a platform for AI-assisted testing if you haven’t automated your deployments. AI amplifies what already exists \u2014 it doesn’t create capability from nothing.<\/p>\n\n\n\n For testing teams, this means the fundamentals still matter enormously. Test automation, continuous integration, test data management, and a learning culture are prerequisites for any meaningful AI adoption. Teams that skip straight to “let’s use an AI test generator” without solid automation foundations invariably discover that their AI-generated tests are unreliable, unmaintainable, or simply wrong.<\/p>\n\n\n\n The model also reinforces something experienced testers already know: culture eats tools for breakfast<\/strong>. Capabilities like generative organizational culture, team experimentation, and transformational leadership remain just as important in an AI-augmented world. A team that doesn’t feel safe admitting mistakes won’t suddenly embrace transparency just because an AI dashboard exists.<\/p>\n\n\n\n The DORA AI Capabilities Model doesn’t prescribe a one-size-fits-all roadmap. But its structure suggests a clear starting point: assess your foundations before chasing AI features<\/strong>. Here’s a practical sequence:<\/p>\n\n\n\n The Ministry of Testing community frames this well: “AI amplifies the good and the bad, so where should your team start?” The answer, supported by the DORA model, is clear. Start by making sure there’s more good than bad for AI to amplify.<\/p>\n\n\n\n The DORA AI Capabilities Model is not a call to throw out everything you know about software delivery. It’s a recognition that AI shifts the landscape \u2014 and that teams who invest in data quality, clear policies, shared platforms, and strong fundamentals will be the ones who benefit most from AI-assisted development and testing. For testing teams, the message is reassuring: the skills you’ve been building all along \u2014 automation, critical thinking, collaboration \u2014 are exactly what makes AI work well in practice.<\/strong><\/p>\n\n\n\n Source: “Making sense of the DORA AI Capabilities Model<\/a>” \u2014 Ministry of Testing. Learn more about the DORA capabilities at dora.dev\/capabilities<\/a>.<\/em><\/p>\n\n\n\n Photo: Daniil Komov \/ Pexels<\/em><\/p>\n","protected":false},"excerpt":{"rendered":" Google’s DORA team has expanded its capabilities model for the AI era. Here’s what the new AI-specific capabilities mean for software testing teams \u2014 and where you should start.<\/p>\n","protected":false},"author":2,"featured_media":1280,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_uf_show_specific_survey":0,"_uf_disable_surveys":false,"footnotes":""},"categories":[],"tags":[],"class_list":["post-1281","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\tThe New AI-Specific Capabilities<\/h2>\n\n\n\n
Why Core Capabilities Are the Foundation<\/h2>\n\n\n\n
Where Should Your Team Start?<\/h2>\n\n\n\n
The Bottom Line<\/h2>\n\n\n\n
\n\n\n\n