Architecture and delivery for critical rescue software
How a rescue organisation aligned architecture, teams and processes to speed up the development of life-saving software

Context
The organisation builds software that speeds up and simplifies alerting rescuers for search-and-rescue missions. Its customers are rescue bodies, and its users are professionals and volunteers. The organisation found itself in a position where architecture, teams and organisational structure struggled to grow because of bottlenecks that had built up at several points in the system.
Objectives
- Teach quality development practices by working alongside the team
- Suggest and implement improvement actions across the organisation
- Support and guide refactoring to align architecture with business objectives
Services
To help the organisation reach its goals, we focused first on understanding and analysing both the organisational dynamics and the health of the software. We then acted to improve collaboration and technical practices. These improvements kicked off a systemic programme that is now building a better Consistency Model (alignment between software architecture, organisational structure and business).
The programme started with an analysis of the software's health, which we now offer as a technical debt assessment, and continued with legacy code refactoring.
Activities
Key results
Services
Key services activated
Consistency
Consistency Model
Practices
Collaboration and technical practices
Architecture
With business objectives
Notes from the project
By joining the team, we supported the development of new features, helped improve the technical practices in use, and improved collaboration among everyone involved in building the product.
Project details
Skills
Tags
Working on something similar?
Let's talk about how we can help you get the results you need.
Book a callTell us where you're stuck
A fragile prototype, a burdensome legacy codebase or unpredictable delivery: that's where we start