- How is it different from the Technical Debt Assessment?
- The Technical Debt Assessment looks at the code and delivers a debt map with priorities and a 90- and 180-day plan. The Software Delivery Assessment looks at code, practices, process, organisation and AI use to find where work waits, from backlog to production. When the bottleneck turns out to be in the code, the two complement each other.
- How does it differ from the AI assessment for software development?
- The AI assessment for software development is done before introducing AI into development and measures the starting point. This assessment is for when speed is below expectations, with AI or without it, and as far as AI is concerned it looks at how the team uses it today and whether it speeds up the very phase where work slows down.
- We've introduced AI in the team and we aren't releasing more often. Where do we start?
- You start by measuring the whole cycle, because the time gained writing code can be lost in the waits that come afterwards. In Atlassian's 2025 State of Developer Experience report, covering 3,500 developers and managers, 68% say AI saves them more than ten hours a week and 50% say they lose ten or more, largely to organisational inefficiencies. These are self-reported figures, collected by a company that sells developer tools, but they point the same way as the 2025 DORA report.
- How long does it take?
- One to two months, depending on how many teams and products are in scope. The time is needed to observe the flow of work on real data and to listen to everyone involved.
- What access do you need?
- The repository and its history, the release pipeline, the backlog and project management tools, and usage data from AI tools. We agree the scope and the rules on data use with you before we begin.
- Do we have to start with the assessment to work with you?
- No. It is the starting point we recommend when it isn't clear where to intervene. If the bottleneck is already obvious, you can start directly with the service that addresses it.