The Atlassian AI SDLC Index
Insights from DX data on how the AI software development lifecycle (SDLC) is evolving. Latest update 11.18.26
Developer experience
What developers are using AI for
AI use by task
| Category | Work type | Share |
|---|---|---|
| Code review | Code reviews | 10.6 |
| Exploration | Architecture design and planning | 11.9 |
| Exploration | Questions | 7.2 |
| Exploration | Ideation | 1.7 |
| Features | Feature enhancements | 9.9 |
| Features | New features | 4.2 |
| Fixes | Bug fixes | 20.2 |
| Fixes | Build or test failure fixes | 3.9 |
| Fixes | Vulnerability remediation & hardening | 2 |
| Fixes | Data or migration fixes | 1.7 |
| Maintenance | Documentation | 10.5 |
| Maintenance | Refactors and rewrites | 10.3 |
| Maintenance | Test updates | 8.3 |
| Maintenance | Dependency or config updates | 6.4 |
| Maintenance | Performance improvements | 2.2 |
| Other | Other | 4.4 |
| Other | Data generation | 1.1 |
What’s changing for developers
Change in share of organizations rating aspects of their work favorably
| Category | Driver | Percent favorable (2025) | Percent favorable (2026) | Change | Direction |
|---|---|---|---|---|---|
| Dev foundations and tooling | Documentation | 47.7 | 60.4 | 12.7 | Improved |
| Dev foundations and tooling | Dev environment | 61 | 68.1 | 7.1 | Improved |
| Dev foundations and tooling | Build and test | 57.3 | 60.8 | 3.5 | Improved |
| Dev foundations and tooling | Code maintainability | 77.2 | 79.6 | 2.4 | Improved |
| Feedback and operational safety | Production debugging | 52.9 | 61.6 | 8.7 | Improved |
| Feedback and operational safety | Change confidence | 79.7 | 78.7 | -1 | Declined |
| Feedback and operational safety | Local iteration speed | 77.3 | 74.6 | -2.7 | Declined |
| Feedback and operational safety | Incident handling | 87.3 | 84.4 | -2.9 | Declined |
| Direction and coordination | Planning process | 64.5 | 65.3 | 0.8 | Improved |
| Direction and coordination | Decision-making | 65.8 | 66.6 | 0.8 | Improved |
| Direction and coordination | Cross-team collaboration | 56.5 | 57.2 | 0.7 | Improved |
| Direction and coordination | Clear direction | 74.1 | 72.1 | -2 | Declined |
| Focus and energy | Deep work | 59 | 63.4 | 4.4 | Improved |
| Focus and energy | Engagement | 63.1 | 64.7 | 1.6 | Improved |
Most impactful drivers of developer experience
Elements of a developer’s day-to-day work that drive the highest impact across key outcomes (Speed, Quality, Ease of Delivery, and Ease of Release) and how developers rate them today
| Driver | Favorability | Impact | Outcome | Quadrant | Callout number | Description |
|---|---|---|---|---|---|---|
| Production debugging | 63.6 | 0.57 | Speed | Fix first | 1 | High impact, low favorability |
| Decision-making | 66.7 | 0.5 | Speed | Maintain | 2 | High impact, high favorability |
| Documentation | 61.5 | 0.47 | Speed | Fix first | 3 | High impact, low favorability |
| Incident handling | 86.4 | 0.46 | Speed | Maintain | 4 | High impact, high favorability |
| Cross-team collaboration | 57.7 | 0.42 | Speed | Fix first | 5 | High impact, low favorability |
| Dev environment | 68.8 | 0.4 | Speed | Maintain | 6 | High impact, high favorability |
| Change confidence | 79.2 | 0.39 | Speed | Maintain | 7 | High impact, high favorability |
| Local iteration speed | 75.4 | 0.34 | Speed | Lower impact | ||
| Engagement | 65.1 | 0.34 | Speed | Lower impact | ||
| Deep work | 62.8 | 0.32 | Speed | Lower impact | ||
| Build and test | 61.6 | 0.3 | Speed | Lower impact | ||
| Planning process | 64.5 | 0.27 | Speed | Lower impact | ||
| Code maintainability | 80 | 0.21 | Speed | Lower impact | ||
| Clear direction | 71.7 | 0.21 | Speed | Lower impact | ||
| Incident handling | 86.4 | 0.73 | Quality | Maintain | 1 | High impact, high favorability |
| Change confidence | 79.2 | 0.67 | Quality | Maintain | 2 | High impact, high favorability |
| Local iteration speed | 75.4 | 0.6 | Quality | Maintain | 3 | High impact, high favorability |
| Planning process | 64.5 | 0.59 | Quality | Fix first | 4 | High impact, low favorability |
| Documentation | 61.5 | 0.56 | Quality | Fix first | 5 | High impact, low favorability |
| Clear direction | 71.7 | 0.53 | Quality | Maintain | 6 | High impact, high favorability |
| Code maintainability | 80 | 0.53 | Quality | Maintain | 7 | High impact, high favorability |
| Production debugging | 63.6 | 0.53 | Quality | Lower impact | ||
| Build and test | 61.6 | 0.45 | Quality | Lower impact | ||
| Deep work | 62.8 | 0.43 | Quality | Lower impact | ||
| Dev environment | 68.7 | 0.43 | Quality | Lower impact | ||
| Engagement | 65.1 | 0.42 | Quality | Lower impact | ||
| Cross-team collaboration | 57.7 | 0.37 | Quality | Lower impact | ||
| Decision-making | 66.7 | 0.35 | Quality | Lower impact | ||
| Production debugging | 63.6 | 0.48 | Ease of delivery | Fix first | 1 | High impact, low favorability |
| Documentation | 61.5 | 0.45 | Ease of delivery | Fix first | 2 | High impact, low favorability |
| Incident handling | 86.4 | 0.44 | Ease of delivery | Maintain | 3 | High impact, high favorability |
| Change confidence | 79.2 | 0.39 | Ease of delivery | Maintain | 4 | High impact, high favorability |
| Local iteration speed | 75.4 | 0.38 | Ease of delivery | Maintain | 5 | High impact, high favorability |
| Cross-team collaboration | 57.7 | 0.38 | Ease of delivery | Fix first | 6 | High impact, low favorability |
| Dev environment | 68.7 | 0.37 | Ease of delivery | Maintain | 7 | High impact, high favorability |
| Engagement | 65.1 | 0.35 | Ease of delivery | Lower impact | ||
| Decision-making | 66.7 | 0.34 | Ease of delivery | Lower impact | ||
| Planning process | 64.5 | 0.31 | Ease of delivery | Lower impact | ||
| Build and test | 61.6 | 0.31 | Ease of delivery | Lower impact | ||
| Code maintainability | 80 | 0.29 | Ease of delivery | Lower impact | ||
| Clear direction | 71.7 | 0.26 | Ease of delivery | Lower impact | ||
| Deep work | 62.8 | 0.2 | Ease of delivery | Lower impact | ||
| Build and test | 61.6 | 0.64 | Ease of release | Fix first | 1 | High impact, low favorability |
| Incident handling | 86.4 | 0.55 | Ease of release | Maintain | 2 | High impact, high favorability |
| Documentation | 61.5 | 0.5 | Ease of release | Fix first | 3 | High impact, low favorability |
| Production debugging | 63.6 | 0.5 | Ease of release | Fix first | 4 | High impact, low favorability |
| Change confidence | 79.2 | 0.48 | Ease of release | Maintain | 5 | High impact, high favorability |
| Dev environment | 68.7 | 0.45 | Ease of release | Maintain | 6 | High impact, high favorability |
| Local iteration speed | 75.4 | 0.42 | Ease of release | Maintain | 7 | High impact, high favorability |
| Decision-making | 66.7 | 0.4 | Ease of release | Lower impact | ||
| Planning process | 64.5 | 0.39 | Ease of release | Lower impact | ||
| Cross-team collaboration | 57.7 | 0.36 | Ease of release | Lower impact | ||
| Clear direction | 71.7 | 0.34 | Ease of release | Lower impact | ||
| Deep work | 62.8 | 0.3 | Ease of release | Lower impact | ||
| Engagement | 65.1 | 0.29 | Ease of release | Lower impact | ||
| Code maintainability | 80 | 0.27 | Ease of release | Lower impact |
High impact, low favorability
- Build and test
- Documentation
- Production debugging
High impact, high favorability
- Incident handling
- Change confidence
- Dev environment
- Local iteration speed
August–October 2026 (n = 385 companies). Scores vary slightly from the previous chart due to varying sample sizes.”
Friction
What’s slowing developers down
Time lost to friction
20%
Developers lose one in five (20%) workdays to friction. That’s equivalent to about 10 work weeks per year.
- Time lost to friction
- Other work time
| Segment | % of work hours | Total hours per year | Total days per year |
|---|---|---|---|
| Time lost to friction | 20% | 409 Hrs | 51 Days |
| Other work time | 80% | 1631 Hrs | 204 Days |
Hours lost per year, by source
State of PR reviews
Minutes to first review, by share of code that is AI-authored
Review load per developer over time
| Month | PR reviews per person, per month |
|---|---|
| 2026-01 | 12.8 |
| 2026-02 | 13.8 |
| 2026-03 | 16.3 |
| 2026-04 | 15.8 |
| 2026-05 | 15 |
| 2026-06 | 17.2 |
| 2026-07 | 18 |
| 2026-08 | 17.5 |
| 2026-09 | 19.3 |
| 2026-10 | 22.3 |
Impact
Time spent on innovation
Share of developer time spent building new features and capabilities
- Time spent on innovation
- Time spent on all other tasks
| Segment | Share |
|---|---|
| Time spent on innovation | 58.4% |
| Time spent on all other tasks | 41.6% |
Over time
| Month | Time spent on innovation |
|---|---|
| 2025-01 | 55.3% |
| 2025-02 | 54.9% |
| 2025-03 | 54.9% |
| 2025-04 | 56.8% |
| 2025-05 | 55.3% |
| 2025-06 | 56.5% |
| 2025-07 | 56.1% |
| 2025-08 | 57% |
| 2025-09 | 56.3% |
| 2025-10 | 55.4% |
| 2025-11 | 55.8% |
| 2025-12 | 57.6% |
| 2026-01 | 56.8% |
| 2026-02 | 56.5% |
| 2026-03 | 56.9% |
| 2026-04 | 56.8% |
| 2026-05 | 56.8% |
| 2026-06 | 56.9% |
| 2026-07 | 57.7% |
| 2026-08 | 58.5% |
| 2026-09 | 58.4% |
| 2026-10 | 57.8% |
How much code AI authors vs. how much survives
Trending percent of AI-authored code and survivorship
| Month | AI-authored code | AI-authored code that survives |
|---|---|---|
| 2026-04 | 49% | 79.9% |
| 2026-05 | 54.7% | 79.7% |
| 2026-06 | 56.4% | 75.1% |
| 2026-07 | 59.4% | 66% |
| 2026-08 | 65.5% | 61.8% |
| 2026-09 | 63.5% | 58.9% |
| 2026-10 | 69.7% | 68.2% |
AI spend and automation
AI spend per unit of output over time
| Month | AI spend in USD |
|---|---|
| 2026-04 | $8.85 |
| 2026-05 | $17.84 |
| 2026-06 | $23.83 |
| 2026-07 | $32.33 |
| 2026-08 | $38.77 |
| 2026-09 | $39.98 |
| 2026-10 | $29.11 |
Share of PRs that get a bot review over time
| Month | Percent of PRs with bot review |
|---|---|
| 2025-11 | 15.3% |
| 2025-12 | 15.9% |
| 2026-01 | 16.4% |
| 2026-02 | 17.1% |
| 2026-03 | 18% |
| 2026-04 | 19.3% |
| 2026-05 | 19.7% |
| 2026-06 | 20.5% |
| 2026-07 | 21% |
| 2026-08 | 21.6% |
| 2026-09 | 21.6% |
| 2026-10 | 21.2% |
See how engineering teams are scaling agentic AI across real work
Methodology
DX is an engineering intelligence platform designed to help engineering organizations measure and improve software health, developer productivity, and AI-human collaboration for a truly AI-first SDLC.
The dataset represents a sample of more than 340,000 engineers at 500+ engineering organizations that use the DX platform. Companies range in size from fewer than 50 to over 10,000 employees, represent a wide geographic spread from Europe to Asia to North America, and encompass many industries, including finance, retail/e-commerce, and healthcare. All self-reported and telemetry data are aggregated at the company level, which means that team-level variation within organizations is not captured.
