IT groups have been struggling to find and retain software developer talent for a while. And amid a shrunken tech economy, technology leaders are trying to find ways to do more with less. One of the effects of this condition has been increased investment into internal developer portals (IDPs) to support engineering teams. These IDPs centralize tools and standardize common DevOps workflows to help realize the ambitions of platform engineering.
The goal is for IDPs to enhance software agility and, in the process, improve developer productivity. But has this been the case? What is the status of these IDP initiatives? And most importantly, have these initiatives successfully enhanced productivity without sacrificing developer experience or developer satisfaction?
Below, we’ll attempt to answer these questions. We’ll look at the state of internal developer portals and consider how they streamline developer productivity and improve developer experience.
The State of Internal Developer Portals
In 2023, developer productivity engineering became a major talking point. Although developer productivity measurement frameworks sparked a heated debate in the software community, organizations still appear to be making prioritizing developer productivity a goal.
For instance, 87% of respondents said that improving developer productivity is a top software development action, according to a 2023 whitepaper commissioned by Humanitec. This was the number-one prioritized software goal, ahead of addressing IT’s backlog, improving supply chain governance and speeding up cycle time.
One way to enable productivity is by streamlining the developer workflow with internal developer portals. This trend is still in its early stages, but we saw the tides turning in 2023. Nearly all organizations have already begun implementing platform engineering, and “85% of respondents surveyed have either started implementing internal developer portals or are planning to do so in the next year,” according to the 2024 State of Internal Developer Portals report by Port.
It’s hard to talk about developer portals without mentioning Backstage, the incubating CNCF project open-sourced by Spotify. Backstage saw significant adoption in 2023. (At the time of writing, it’s the 12th most-active CNCF project in terms of GitHub activity).
The emergence of IDP reference architectures has also helped to paint a clearer picture of what portals to manage infrastructure look like in practice. That said, the market is still maturing, and organizations are unsure what constitutes an IDP. As such, 53% utilize various forms of developer portals, including in-house, Backstage and commercial products, the Port report found.
Do IDPs Enhance Developer Productivity and Satisfaction?
Increased developer productivity is the primary measure of success for an internal developer portal initiative. However, determining how to compute this productivity is still a moving target. One such metric could be monitoring the time spent on toil-intensive activities, specifically non-coding work, which peaks for teams not adopting platform engineering. For those organizations not engaged in platform engineering, 78% of respondents reported three or more hours of developers’ time was spent daily on non-core work, found the Port report.
Productivity could also be measured in terms of deployment frequency, or how long it takes per deployment. But going beyond traditional developer productivity metrics, IT leaders can consider other indicators to gauge productivity, says Paolo Negri, CTO and co-founder of Contentful. First is the ‘health’ side of productivity, he said. “If you look at software development alone, where does my organization stand comparatively to some sort of productivity benchmark with other similar organizations?”
Second is thinking about cross-functional productivity. “What is the highest productivity or performance we can achieve when considering what the business is trying to accomplish?” added Negri. “This line of thinking is more about the essential aspects to accelerate the cross-functional workflow by reducing the single team dependency on the development process, freeing up a team to focus on higher return activities.”
How this productivity is measured is still up for debate, but more appear to be utilizing qualitative measurements versus quantitative ones. A full 75% of respondents in the aforementioned Port study said they preferred surveys or custom reporting instead of standard frameworks like DORA or SPACE. LinkedIn, for example, has done some interesting work building a custom internal survey platform to collect feedback to improve developer satisfaction with internal tools.
“Platform engineers can significantly enhance the developer experience by building a tight information loop to identify pain points and gather dev feedback,” added Conor Bronsdon, host of LinearB’s Dev Interrupted podcast. “This requires both actively soliciting developer input via surveys and using quantitative measures like local build times and cycle time to understand and track workflow blockers.”
Streamlining The Developer Toolchain
Interestingly, developers say they spend as much time waiting for builds and tests as they do writing code, according to a GitHub survey of 500 companies with over 1,000 employees (June 2023). The hope is that IDPs can free up a team to reduce time spent on such tasks and focus on higher returns. A vital component of this enablement will be reducing developer friction with their toolchain.
“Developer Productivity Engineering is all about maximizing the amount of time available for productive work by minimizing the amount of time developers spend on toil and frustrating tasks like waiting for long feedback cycles to complete and avoidable and inefficient troubleshooting,” said Hans Dockter, CEO of Gradle. As such, there is a good argument for seeing how we can reduce friction in the developer workflow.
Above all, Dockter encourages technology leaders to focus on reducing context-switching, a primary contributor to cognitive fatigue. “Most leaders today do not fully understand the workflow and mental experience of their developers since most don’t experience the pains directly,” he said. “In order to improve developer productivity and achieve the best possible developer experience, I believe it’s essential for technology leadership to consider the cognitive science that drives developer behavior.”
Hope is on IDPs to Retain Productivity
It can be challenging to manage software teams and keep output consistent throughout periods of economic downturn. However, many are bullish on IDPs and platform engineering to retain (if not increase) software agility.
“Integrated development platforms (IDPs) with platform engineering support to extend workflow automation throughout the software development lifecycle can streamline the development process, directly boosting productivity,” said Bronsdon. “By automating routine tasks, providing standardized development environments, and facilitating continuous integration and deployment, platform engineering accrues efficiency benefits across the R&D organization.”
Regardless of the exact implementation, the IDP concept remains a popular method to allow developers to focus more on creating business value and less on the logistics of the development process. As such, I expect continued development and benchmarks to emerge in this new era of DevOps throughout the year ahead.
