Modernisation Sprint
„The app stopped in 2017 — tooling, tests, release process.“
A modernisation sprint brings a defined part of your iOS app up to date: module by module, instead of rewriting everything at once. Two to four weeks per sprint, fixed price, defined outcome. The app stays releasable throughout.
- Duration
- 2–4 weeks per sprint
- Price
- Fixed price
- Outcome
- Migrated module, CI/CD, test suite
The tooling has stalled: old Swift or Objective-C, no modern concurrency, sluggish builds.
There are hardly any tests. Every release is a risk, every change means flying blind.
The release process is manual and depends on one person.
Dependencies can no longer be updated, and new iOS versions become a problem.
- 01upfront
Scoping
Which module, which goal, what is explicitly out of scope — recorded in writing. The basis is an audit or your own prioritisation.
- 022–4 weeks
Sprint
Migration of the module, tests, CI/CD — in short, traceable steps, in parallel with normal operation.
- 03at the end
Review
The module runs in production, the test suite runs in CI. A joint look at the result against the agreed scope.
- 04as needed
Next sprint
Each further sprint is commissioned individually. No framework contract, no subscription. You decide anew after each result.
After each sprint there is a finished, usable state: a migrated module in production, a CI/CD pipeline and a test suite that catches regressions. No months of old and new running in parallel, no rewrite risk. The progress is visible and usable after every sprint.
- Why sprints instead of a full rewrite?
- A rewrite promises a clean start and usually delivers standstill: two codebases for months, no releases, growing risk. Sprints deliver usable intermediate states, and you can stop after any of them.
- What does a sprint cost?
- A fixed price per sprint, quoted after scoping. The scope is defined in writing beforehand, and so is the price.
- Do you work alongside our team?
- Yes, that is the normal case: PR-based work in the existing repository, CI integration, short check-ins. The knowledge stays with your team.
- How do we know which module comes first?
- From an architecture audit, or from your own prioritisation if the pain points are clear. Scoping validates the choice either way.
Quote after a free first conversation
First conversation: 30 minutes, free of charge, no presentation.
You describe the situation, I tell you whether and how I can help. No slides, no sales pitch.