DevOps and delivery
Source control, automated builds, testing and deployment, so releasing software is routine rather than an event.
DevOps covers the plumbing that gets code from a developer’s machine into production. Source control, automated builds, tests that run on every change, and deployments that happen the same way each time.
I’ve moved long-running software businesses onto GitHub, split sprawling repositories along sensible boundaries, and set up pipelines so that a release is a short, repeatable step. On older products this work often comes first, because everything else in a modernisation depends on being able to ship safely.
The payoff is confidence. When the easy path is also the correct path, teams release more often and recover faster when something goes wrong.
Related Content
Moving a 20-year-old SaaS product onto GitHub
Lessons learned moving source code, development workflows and operations into the GitHub ecosystem.
The pit of success, in practice
Doing the right thing should be what happens by default. Leaving the path should be possible, but harder. A short list of what that means in practice.
Planning the modernisation of a safety-critical SaaS product
How an advisory engagement took a long-established, safety-critical B2B SaaS product from a vague need to modernise to an evidence-led delivery plan.