On its Inside Atlassian blog, Atlassian publishes a data study co-authored by two data scientists (Robbie Geoghegan, Fan Jiang) measuring the actual return of an AI-native SDLC powered by its Rovo Dev agent. The stakes are framed from the outset around the "productivity paradox" formulated by Robert Solow in 1987 ("you can see the computer age everywhere but in the productivity statistics"): AI is massively adopted — 93% of developers use AI tools, nearly 30% of code is written by AI — but its impact remains unclear as long as it is measured in usage (tokens) rather than impact.
The results, drawn from a quasi-experiment across 3,400 repositories from 2,500 customers (propensity-score matching), are quantified and segmented. Repositories adopting Rovo Dev merge 19% more pull requests per month than non-adopters. The gain rises to 37-51% on low- or medium-activity repositories, and doubles to 59-87% when 3 to 5 members of the team adopt the tool: collective adoption clearly outperforms individual adoption. On the efficiency side, a survey of more than 6,200 developers (estimates taken at the 20th percentile, hence conservative) establishes a gain of 2-3 hours per week on coding and review tasks, or about 10% of the 24 hours they involve — that is, 20-30 hours per week reinvested for a team of ten.
The article proposes a five-stage AI-native SDLC in which the agent supports the human: Plan (proposed breakdowns and estimates), Orchestrate (human/agent coordination), Code (autonomous agents on well-scoped work, PRs ready for review), Review (review against team standards before the human) and Operate (always-on incident copilots). It pairs this with a four-dimension measurement framework: Speed (PR throughput), Efficiency (time saved), Quality (change failure rate) and Satisfaction (developer satisfaction) — so as not to reduce value to velocity alone.
Two points reinforce the argument. First, the role of context: thanks to Atlassian's Teamwork Graph, context-rich AI delivers results that are 44% more accurate while consuming 48% fewer tokens. Second, the operational recommendation: start with a team (not an individual), choose a repository with 3-5 engineers who are actual users, and measure throughput and time savings 2-3 months after deployment, once the novelty effect has worn off. The underlying message: the value of AI is real but conditioned on rigorous impact measurement and team-level adoption.