Navigable retro-specification
Recover business behaviour, requirements, interfaces and system constraints from the software that actually runs, not from documentation that may have drifted.
GOALS · REQUIREMENTS · BEHAVIOUR · INTERFACES
Sprint 0 / Software Discovery
Understand the system
before changing it.
Turn an existing application into a navigable retro-specification, architecture and code graph, an evidence-based assessment and prioritised transformation paths.
01 / What you receive
A current system view.
A credible way forward.
Sprint 0 produces usable engineering artifacts, not a presentation assembled around assumptions. Your teams keep the recovered knowledge and can inspect the basis for every recommendation.
Architecture and code graph
Reconstruct the system’s structure, dependencies, frameworks, boundaries and execution paths into an explorable representation your teams can interrogate.
COMPONENTS · DEPENDENCIES · FLOWS · BOUNDARIES
Risk and quality assessment
Evaluate security, maintainability, architecture, test coverage, deployment context and the constraints that affect any credible transformation programme.
RISKS · VIOLATIONS · CONSTRAINTS · BASELINE
Prioritised transformation paths
Compare realistic routes against your business goals, economics and IT standards so the next investment starts from an explicit, reviewable decision.
OPTIONS · TRADE-OFFS · SEQUENCE · ESTIMATES
02 / How it works
Discovery ends
with a decision.
The engagement is deliberately bounded. We reconstruct the current system, assess it against the question you need answered and close with explicit options for what happens next.
- 01Scope
Agree the system and the question.
Confirm repositories, runtimes, available documentation, access boundaries and the business decision Sprint 0 must support.
- 02Recover
Reconstruct what exists.
Run Discovery locally or remotely to recover the retro-specification, architecture and code graph from the available system evidence.
- 03Assess
Make condition and constraints visible.
Evaluate quality, risk, dependencies and target-state constraints with Solario controls and senior engineering review.
- 04Decide
Select the next transformation path.
Review findings together, choose a remediation or transformation direction, then bring the decision into the governed Intent phase.
Discovery feeds Intent. Business goals, requirements, selected constraints and the chosen path are made explicit and signed off before any delivery workload enters Design.
03 / What Sprint 0 can unlock
Different outcomes.
One informed starting point.
The right answer may be a focused repair, a runtime exit or a multi-year modernisation. Sprint 0 prevents the delivery model from being chosen before the system is understood.
Remediate in place
Fix defects, security violations or technical debt at scale without migrating the application.
Gain runtime independence
Replace licensed SaaS, proprietary middleware or low-code/no-code runtimes with application code you own.
Upgrade the stack
Move legacy languages, frameworks and execution environments forward while preserving intended behaviour.
Modernise the architecture
Reorganise large codebases into a maintainable monolith, clean architecture or a deliberate service split.
Representative engagement / Insurance SaaS
10,000 CSP violations removed from a live Java 6 platform.
Solario remediated the production codebase in a few weeks, against a twelve-month estimate for a conventional programme. The system stayed in place: the immediate objective was safe, governed remediation at scale, not migration for its own sake.
04 / Start with one system
Tell us what you need to understand.
A repository, an application boundary and a decision you need to make are enough to start the conversation. We will respond with the access, scope and people required to shape a credible Sprint 0.
- Best fit
- Existing production applications with meaningful technical or commercial constraints
- Execution
- Remote or local, with source and model access kept inside the agreed perimeter
- Next step
- A short scoping call, followed by a bounded proposal if the system is a fit