- Industry
- IT Company
- Department
- Engineering
- Team
- Application Engineering
- Kind
- Decision-maker
- Approver
- Engineering Manager
- Code
- ENG-10
It finds the code that costs most to keep on the SaaS platform and in long-running managed-services engagements, from churn, linked defects, complexity, slow builds and support hours, estimates what fixing it would save in engineering hours and USD, and ranks a refactoring backlog. It keeps debt work within the sprint capacity agreed with product or the client.
How it works
7 steps, and a person signs off before step 7.
- 01Looks it up
Finds the record the request is about in the source code repository and CI/CD: churn, complexity, build times and linked defects for the repositories named..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Forecasts, when it decides
Projects what each option will cost or return before it recommends one.
- 05Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 06Asks a person
Hands the work to Engineering Manager with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the project management tool: it creates the approved debt items in the backlog with estimates. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The technical debt policy: hotspot measures, cost model (blended engineering rate), sprint capacity for debt, refactoring rules and what a client must agree before debt work is billed.
Reads from
the source code repository and CI/CD: churn, complexity, build times and linked defects for the repositories named.
Acts in
the project management tool: it creates the approved debt items in the backlog with estimates.
Hands back
A ranked list of items, each with path, problem, effort_hours, saving_usd_per_sprint, payback_sprints, billable (true or false) and test_plan.
Asks a person when
The backlog takes more than 15 percent of capacity, or debt work would be billed to a client.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Sprint capacity for debt (%) | 15 | Debt work takes at most this share of a sprint. |
| Hotspot window (days) | 90 | Churn and defects are counted over this window. |
| Blended engineering rate (USD per hour) | 95 | Used to price the cost of debt and the saving from fixing it. |
| Pays back within (sprints) | 6 | Only items that pay back within this many sprints are proposed. |
| Billable debt work needs a change request | On | When on, debt work billed to a client needs an approved change request. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Count churn and defects over 90 days and price cost at 95 USD an hour.
- Propose only items that pay back within 6 sprints.
- Keep debt work to 15 percent of sprint capacity.
- When on is true, debt work on a client engagement that would be billed waits for an approved change request.
- Rank by saving per hour of effort and give each item a test plan.
See the Technical Debt Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.