<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Catalog on</title><link>https://dora.dev/capabilities/</link><description>Recent content in Catalog on</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 08 Dec 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://dora.dev/capabilities/index.xml" rel="self" type="application/rss+xml"/><item><title>AI-accessible internal data</title><link>https://dora.dev/capabilities/ai-accessible-internal-data/</link><pubDate>Mon, 08 Dec 2025 00:00:00 +0000</pubDate><guid>https://dora.dev/capabilities/ai-accessible-internal-data/</guid><description>AI-accessible internal data is the capability of securely connecting AI systems to an organization’s proprietary information—such as codebases, documentation, and operational metrics—to provide context-aware responses. This practice, often implemented through a discipline known as “context engineering,” transforms generic AI models into specialized experts.</description></item><item><title>Clear and communicated AI stance</title><link>https://dora.dev/capabilities/clear-and-communicated-ai-stance/</link><pubDate>Mon, 08 Dec 2025 00:00:00 +0000</pubDate><guid>https://dora.dev/capabilities/clear-and-communicated-ai-stance/</guid><description>A clear and communicated AI stance is an organization&amp;rsquo;s official, widely understood position on how developers are expected and permitted to use AI tools. It moves beyond restrictive policies to provide practical guardrails, ensuring developers know which tools are allowed, which data is safe to use, and that the organization supports their experimentation.</description></item><item><title>Healthy data ecosystems</title><link>https://dora.dev/capabilities/healthy-data-ecosystems/</link><pubDate>Mon, 08 Dec 2025 00:00:00 +0000</pubDate><guid>https://dora.dev/capabilities/healthy-data-ecosystems/</guid><description>A healthy data ecosystem is characterized by internal data that is robust, trustworthy, and easily accessible to both teams and tools. It moves beyond data as a by-product of transactions to treating data as a product itself. This capability is a critical prerequisite for AI adoption, ensuring that individual productivity gains from AI translate into systemic organizational performance.</description></item><item><title>Platform engineering</title><link>https://dora.dev/capabilities/platform-engineering/</link><pubDate>Mon, 08 Dec 2025 00:00:00 +0000</pubDate><guid>https://dora.dev/capabilities/platform-engineering/</guid><description>Platform engineering is the discipline of designing and building toolchains and workflows that enable self-service capabilities for software engineering organizations in the cloud-native era. Platform engineers provide an integrated product most often referred to as an &amp;lsquo;Internal Developer Platform&amp;rsquo; covering the operational necessities of the entire lifecycle of an application.</description></item><item><title>User-centric focus</title><link>https://dora.dev/capabilities/user-centric-focus/</link><pubDate>Mon, 08 Dec 2025 00:00:00 +0000</pubDate><guid>https://dora.dev/capabilities/user-centric-focus/</guid><description>User-centric focus is the degree to which teams prioritize the needs, feedback, and experiences of the people who use their software. It acts as a compass, ensuring that the velocity gained through technical capabilities like AI and continuous delivery is directed toward valuable outcomes.</description></item><item><title>Code maintainability</title><link>https://dora.dev/capabilities/code-maintainability/</link><pubDate>Mon, 27 Mar 2023 09:48:50 +0100</pubDate><guid>https://dora.dev/capabilities/code-maintainability/</guid><description>Systems and tools that make it easy for developers to change code maintained by others, to find examples in the codebase, to reuse other people&amp;rsquo;s code, and to add, upgrade, and migrate to new versions of dependencies without breaking their code.</description></item><item><title>Continuous delivery</title><link>https://dora.dev/capabilities/continuous-delivery/</link><pubDate>Mon, 27 Mar 2023 09:48:50 +0100</pubDate><guid>https://dora.dev/capabilities/continuous-delivery/</guid><description>&lt;p&gt;Teams can be said to have implemented continuous delivery when they have achieved the following outcomes:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Teams can deploy to production (or to end users) on demand, throughout the software delivery lifecycle.&lt;/li&gt;
&lt;li&gt;Fast feedback on the quality and deployability of the system is available to everyone on the team, and people make acting on this feedback their highest priority.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Continuous delivery requires the implementation of a number of technical practices including continuous integration, trunk-based development, the comprehensive use of version control, and continuous testing.&lt;/p&gt;
&lt;p&gt;In turn, continuous delivery drives a number of outcomes: higher software delivery performance, better organizational culture, less rework, lower deployment pain, and less burnout.&lt;/p&gt;</description></item><item><title>Continuous integration</title><link>https://dora.dev/capabilities/continuous-integration/</link><pubDate>Mon, 27 Mar 2023 09:48:50 +0100</pubDate><guid>https://dora.dev/capabilities/continuous-integration/</guid><description>A development practice where code is regularly checked in, and each check-in triggers a set of quick tests to discover regressions, which developers fix immediately. The CI process creates canonical builds and packages that are ultimately deployed and released.</description></item><item><title>Database change management</title><link>https://dora.dev/capabilities/database-change-management/</link><pubDate>Mon, 27 Mar 2023 09:48:50 +0100</pubDate><guid>https://dora.dev/capabilities/database-change-management/</guid><description>Database changes don&amp;rsquo;t slow teams down if they follow a few key practices, including storing database changes as scripts in version control (and managing these changes the same way as production application changes), making database changes visible to everyone in the software delivery lifecycle (including engineers), and communicating with all parties when changes to the application require database changes.</description></item><item><title>Deployment automation</title><link>https://dora.dev/capabilities/deployment-automation/</link><pubDate>Mon, 27 Mar 2023 09:48:50 +0100</pubDate><guid>https://dora.dev/capabilities/deployment-automation/</guid><description>The degree to which deployments are fully automated and do not require manual intervention.</description></item></channel></rss>