Technical debt optimizer for development teams

The new platform gives developers a boost to balance reliability against new features; automates Jira creation for early warning at team level of technical debt risk

WALTHAM, Mass., November 16, 2021– (BUSINESS WIRE) – Nobl9, the leader in software reliability, today launched Hydrogen, the first platform designed to identify technical debt impacting customers in a way that engineers and stakeholders can understand. Hydrogen gives software reliability issues their own Agile workflow, so teams can break the cycle of neglecting the very issues that cause arduous on-call rotations, preventable outages, and technical burnout.

Modern software developer tools and workflow emphasize the speed of delivery of new functionality, but most organizations fall into a tendency to stall known reliability and technical debt issues in Jira backlogs, where they disappear until things stop in production. This “technology debt” covers everything from known bugs to security fixes, testing, performance management strategies, and many other software reliability issues.

When software crashes do occur, many underlying causes were known from the start, but never prioritized. The on-call teams run out and the cycle begins again with the next feature sprint.

“Organizations that view their enterprise architecture as their technology architecture use software development and deployment as a competitive weapon,” said Stephen Elliot, group vice president of DevOps, I&O and Cloud Operations at IDC. “Under this operating model, the role of automation and technical debt management with the development of new features becomes an important set of capabilities for developers, DevOps and engineering teams. reliability of the site.

Presentation of hydrogen

Jira is great for prioritizing development efforts, but prioritizing software reliability issues requires a lot more context and live data. Hydrogen is the premier platform that helps engineering teams define software reliability requirements, have the data to prove to the business when tech debt issues become the highest priority, and bring that data back. in Jira. In three simple steps, Hydrogen can give developers the information they need to take control of technical debt in the context of their Jira milestones.

“We saw with Hydrogen an opportunity to model the amount of unreliability that development teams are willing to accept. This applies not only to incidents, but also to alerts when their technical debt needs to be targeted, enabling a data-driven approach to prioritizing technology debt, ”said Brian Singer, Product Manager and Co-Founder of Nobl9. “Hydrogen allows teams to build tech debt directly into their arrears and integrate that work directly into sprints if they are using Agile methodologies, so that issues impacting the health of the system leading to outages and downtime. Pager fatigue are treated as part of the regular development process. “

Software Defined Service Level Objectives (“SLO”)

What you cannot measure, you cannot improve. SLOs are software-defined reliability targets that can be used for both reporting and automation. As customer expectations and business needs change, SLOs can be refined to uncover the optimal point on the cost-service = level curve. SLOs are traditionally used to identify risks associated with execution, known as error budgets. Hydrogen adds the ability to identify technical debt risks impacting the business.

Connect your APMs and logging tools

Hydrogen supports many existing metrics sources including Datadog, New Relic, Splunk, Google BigQuery, AppDynamics, Thousand Eyes, Dynatrace, Prometheus, and more. Hydrogen allows you to quickly connect the data you already have to goals of reliability, error rates and (un) acceptable technical debt.

Define your error and technical budget policies

Once you collect data and set thresholds based on current understanding of user expectations, Hydrogen automates workflows based on expected quality policies and engineering decisions. When a particular service is at risk, which means its metrics tend to violate set targets, the team can be notified through multiple channels and new technical debt related work items are filed in the Jira backlog.

Bringing visibility to technical debt in the tool where feature planning is already underway breaks the cycle of ignoring systemic risks in favor of shipping features.

Finally, a way to balance functionality with reliability

Hydrogen gives engineering teams confidence by inserting precise context into the tech debt planning cycle – no more sweeping tech debt under the rug, or exaggerating the risks of service without business impact. Now developers can measure what was killing on-call teams, hurting user happiness, and frustrating management.

Consolidated view of service status

Hydrogen has a new service health dashboard that organizes SLOs into logical groups mapped to features via tags. This provides insight into the technical risks of debt at any level of the organization.

Automatically created Jira tickets for services with growing tech debt

When technical debt increases, Hydrogen takes automated action on your behalf to ensure that sprint planners and scrum masters see the manifestation of risk in the system. In addition to technical debt relief planning, Hydrogen can trigger a variety of automated workflows to escalate service deterioration that may require further investigation outside of a full-blown incident.

A boost for the right speed to keep delivery optimized

Engineering teams need to find a sustainable pace of innovation to continue delivering value to customers. Over time and between multiple teams, Hydrogen may enforce code release policies based on technical debt budgets. This means adding Continuous Integration and Delivery Automation (CICD) depending on whether a code change is marked as an improvement in technology debt or functionality. Over time, this data provides a clear picture of where the investment is going and the right speed to ensure stability, the customer

engineering satisfaction and productivity.

What customers are saying

“There has always been a mismatch between the business need to satisfy customers and the balance between that and the priority given to technology debt,” said Kristian Dell’Orso, vice president of engineering at the reliability of the sites at Flexera. “Nobl9 gave us the impetus to balance these two very difficult issues, and the result is that we now have a very clear understanding of when it’s time to prioritize software reliability over functionality, and vice versa. translates into a happier and more productive team of engineers, always confident of the meaningful impact of their work. “

“No engineering team wants to cry wolf about a potentially very serious technological debt, but they don’t want to ignore it either,” said Zachary Nickens, SRE team captain at OutSystems. “When we decided to build our own technology debt management platform using SLOs, we estimated that it would take two years and $ 3 million in engineering hours. Hydrogen is the first platform we’ve seen that finds the right place – to draw a straight line from technical debt to customer impact, and costs a fraction of what we would have spent on it. build ourselves. “

“I see Hydrogen being technical debt what Atlassian is to feature development,” said Thad West, CEO of Isos Technology, a Nobl9 reseller specializing in Agile methodology and who is also one of the largest resellers of Agile. ‘Atlassian. “Hydrogen brings new visibility into the underlying risks that are buried in the backlog of technical debt issues, and it’s the first practical solution that gives teams a language to speak up and mitigate those risks. “

Getting started with Nobl9 Hydrogen
Register to access it:

About Nobl9

Nobl9, the software reliability platform company, continues the noble pursuit of reliable software. Founded by Marcin Kurc and Brian Singer, who joined Google through the acquisition of Orbitera, Nobl9 helps software developers, DevOps practitioners and reliability engineers deliver reliable functionality faster through service level objectives software-defined that connect monitoring and other logging and tracing data to user happiness. and business KPIs. The company is backed by Battery Ventures, CRV, Bonfire, Harmony, Resolute, and Sorenson and is headquartered in Boston with a distributed team. More information on and in the Nobl9 free resource library.

See the source version on


Heather fitzsimmons
RP Mindshare
[email protected]

Comments are closed.