A critical database hardware failure due to insufficient RAM highlighted the risks of physical infrastructure and became the catalyst for moving to the cloud.
The migration was structured using agile principles, including a clear vision, a tight three-month deadline to create focus, and empowering a cross-functional team.
The core legacy database migration was de-risked by breaking it into smaller pieces, deleting obsolete tables, and using a risk-based, iterative approach.
Gaining support from product and finance stakeholders required framing the technical migration in terms of business value, such as faster releases and increased developer productivity.
The team was given the freedom to determine their own process, while a public burndown chart of servers and applications created transparency and motivated progress.
The final cutover was managed with clear communication channels, a reserve engineer for unforeseen issues, and deliberate over-provisioning of the new database to ensure a smooth launch.
Success depended on having a single clear goal, maintaining transparency, slicing large tasks, showing developers direct value, and engaging business stakeholders early.
The discussion covers what could be improved, how to explain agile benefits to non-technical stakeholders, and the rationale for choosing AWS over other cloud providers.
28:12Josip Stuhli
45:12Sébastien Stormacq
25:48Elisabeth Günther
24:22Jürgen Pilz
29:31Pierre-Luc Noel & Fritz Reichmann
34:46Bruno Amaro Almeida
46:48Stefan Priebsch
42:23Adam Bien
.gif?w=240&auto=compress,format)
Jobs that call for the skills explored in this talk.
SYCOR GmbH
Göttingen, Germany
Fritz Logistik GmbH
Heilbronn, Germany
