Keeping a software portfolio running
YRW Technologies builds and scales a portfolio of software products. Depra maintains and builds their internal projects — the tools, integrations and platform work that sits underneath a multi-product business.
- Client
- YRW Technologies
- Based in
- Alexandria, NSW, Australia
- Engagement
- Engineering & product support · Ongoing
- Status
- Ongoing engagement
The work that always loses the argument
A company running a portfolio of products has a problem an ordinary product team never faces: the number of codebases grows faster than the number of engineers who understand them. Internal tools, integrations and the long tail of maintenance compete with every new launch, and maintenance always loses that argument.
YRW brought us in to own that work. Our engineers work inside their repositories and their issue tracker on the internal platforms the portfolio runs on — building what is missing, maintaining what already ships, and writing both down as they go.
Practices in play
Scope of work
- Internal platform and tooling development
- Maintenance of existing production applications
- Third-party and service integrations
- Bug triage, reproduction and resolution
- Release verification and regression testing
- Architecture and runbook documentation
Four rules the team works to
Read before writing
Every codebase we take on starts with a reading sprint: how it is put together, what it depends on, what the security and test coverage look like, and a written list of risks. No new feature work is promised until that document exists.
Work on their board, not ours
Their repositories, their tracker, their code review standards, their release process. Nothing about working with us requires them to adopt a Depra tool.
Not done until it is written down
Notes and step-by-step guides ship with the change, not after it. That keeps our team replaceable and the knowledge with the client.
Report on a fixed schedule
A demo every sprint, a written health report each month, and a clear route to reach us when something breaks in production.
What actually changed
Stated plainly. We only publish performance figures once the client has seen and agreed them, which is why there is not a percentage on this page yet.
Maintenance has an owner
Work that used to compete with launches now has its own team and its own schedule, so it stops getting pushed back.
Internal platforms keep moving
Tools and integrations get built and looked after continuously, rather than in bursts between product deadlines.
Knowledge stays with the client
Notes, guides and READMEs are part of finishing a job, so nothing important leaves when a person does.
Service-level targets on this engagement
| Metric | Target |
|---|---|
| Sprint commitment met | ≥ 85% |
| Critical bug turnaround | < 48 hours |
| Documentation coverage of shipped work | 100% |
A client quote will be published here once it has been written and approved by YRW Technologies. We do not paraphrase clients.
Hand us the work nobody wants to own
Maintenance, internal tools, integrations, the long tail of support. We read it first and give you the risk list whether or not you carry on.