Project implementation time savings using coding agents

Coding agents would cut total project time by only a fraction of the savings they deliver on coding itself, according to an analysis of the SEA Data Warehouse dataset covering 1,211 software projects. Across the 289 safety critical projects that spent more than 2 days in the Code phase, the Code phase averaged 32% of total project time, so assuming coding agents cut coding time by 90% and all testing activities by 50% yields shrinking relative savings as total project hours rise, with only around 10 projects showing substantial savings. The analysis notes that 10-15% of time goes to Design, Design review, and Design Inspection phases, and that the 50% testing savings figure is simplistic pending several years of data.

Home https://shape-of-code.com/ Uncategorized https://shape-of-code.com/category/uncategorized/ Project implementation time savings using coding agents Project implementation time savings using coding agents To what extent do the significant savings made from using coding agents reduce the total cost of creating a software system? The SEA Data Warehouse dataset https://shape-of-code.com/2026/07/05/detailed-management-data-on-1211-software-projects/ contains detailed records of time spent in various phases of safety critical projects. Just what is needed to estimate an answer to this question, at least for safety critical software. The development of typical commercial software differs from safety critical software in the amount of effort that goes into requirements, design, documentation, and testing. While the safety critical people claim that it’s all about the processes they follow, there is no evidence to show that any process is better than another. What matters is that the process ensures that the requirements, design, documentation, and testing are good enough for the intended use of the software. When producing code is cheap, teams looking to be paid to create software systems are going to have to add value by delivering the kind of reliability and all encompassing application support that safety critical software is intended to provide. The plot below shows, for the 289 projects that spent more than 2-days Code phase, the fraction of time spent in the most common project phases, ordered by fraction spent in Code phase code+data https://www.shape-of-code.com/code-data/proj-coding-time.tgz : The average percentage of project time spent in the Code phase was 32% does not include time spent in the Code review phase . If we assume that coding agents reduce the time spent on coding by, say, 90%, and on all testing activities by, say, 50%, how much would total project time be reduced? The plot below shows, for the 289 projects, original project time red and estimated LLM project time blue/green; code+data https://www.shape-of-code.com/code-data/proj-coding-time.tgz : The general pattern visible is that as the number of project hours increases, the relative LLM saving shrinks. Around 10+ projects show substantial savings. It’s possible that use of coding agents will increase the amount of time developers spend in the Code review phase after any LLMs savings made in this phase . The 50% savings across all testing activities is very simplistic, and we will have to wait a few years for things to settle down and data to become available. Around 10-15% of time is spent in Design, Design review, Design Inspection phases. Will LLMs save a significant amount of time for these phases, or should people continue to be hands-on for this work? Experienced developers are well aware that coding agents have not removed the need for software developers. This post provided some data+analysis showing that developers are still needed, although the number of the people having this job title will decrease. Perhaps the software developer job title will not exist in 10-years, and this kind of work will be commonly known by another name.