- Industry
- Hotel
- Department
- Engineering
- Team
- Application Engineering
- Kind
- Decision-maker
- Approver
- Head of Hotel Technology
- Code
- ENG-10
It finds the hotel software that costs most to keep (the brittle PMS and channel manager adapters, the rate and tax calculation code, old booking engine modules) from churn, linked incidents, complexity and slow builds, estimates what fixing each would save, and ranks a refactoring backlog by payback. It decides what to refactor next within the share of capacity set aside for debt, and keeps refactors away from the peak season freeze.
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 code repository: the change history, complexity and incident links for the codebases 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 Head of Hotel Technology with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the issue tracker: it creates or reorders the debt tickets in the next sprint. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The engineering health data: hotspot reports, incidents and bugs linked to code, the debt capacity agreement, the release calendar and peak season change freezes.
Reads from
the code repository: the change history, complexity and incident links for the codebases named.
Acts in
the issue tracker: it creates or reorders the debt tickets in the next sprint.
Hands back
A list ranked by payback, each with area, problem, evidence (churn, incidents, complexity), fix, effort_days, saving_per_sprint_days, payback_sprints and first_step.
Asks a person when
The plan uses more than 20 percent of capacity, touches rate, tax or payment code, or lands near 15 December to 5 January, and 1 to 31 July.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Capacity for debt work (%) | 20 | The share of engineering time the ranked backlog may use. |
| Look-back for churn and incidents (days) | 90 | How far back it counts changes and linked incidents. |
| Complexity above which code is a hotspot | 15 | Functions above this cyclomatic complexity count as hotspots. |
| Longest acceptable payback (sprints) | 6 | A refactor that pays back slower than this is not scheduled. |
| Peak season change freeze | 15 December to 5 January, and 1 to 31 July | No refactors are scheduled to release in these periods. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Rank code by cost: churn and linked incidents in the last 90 days, complexity above 15, and build time.
- Code that has caused wrong rates, taxes or folio postings ranks above code that is only slow to change.
- Schedule only refactors that pay back within 6 sprints and fit in 20 percent of capacity.
- Propose small, behaviour-preserving first steps with tests that pin current behaviour.
- Nothing scheduled to release during 15 December to 5 January, and 1 to 31 July.
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.