Support and Maintenance en Lyon
How we work in Lyon
Maintaining and building at once, from month two
There is something in production to watch over and something in development to finish. They are two jobs with different rhythms and they are better kept apart in the budget: in the same pot of hours, every incident eats the next phase's time and nobody understands why it is late.
What is an incident and what is the next phase
The classic argument in every phased project: “this does not work” against “we have not built that yet”. As each phase closes we write down what goes into maintenance and what is still pending. It is not bureaucracy: it stops maintenance turning into free development, or the other way round.
Monitoring from the first deployment
Monitoring is set up with phase one, not once the whole project is finished. Availability, errors and response times, with alerts ordered by severity. A phase just put into production is as fragile as a finished project, and a good deal less run in.
Backups as soon as there is data to lose
The moment the first phase has users, it has information that can be lost. Daily backups off the main server and inside the European Union, with restores tested on a separate environment, dated and recorded. Nobody finds out that a backup was useless at a convenient moment.
Answering your questions
What people ask us about Support and Maintenance in Lyon.
If your question is not here, tell us about the project and we will answer with real context.
Ask us directlyReal work
Projects we have built
Full service · All the detail
Support and Maintenance: stack, process, use cases and FAQs