The development of your mobile application or web platform doesn't stop when it goes live. You need to keep the product going, stabilize it, adapt it as it grows, and resolve any problems that may arise. In short, there are many reasons to intervene, and rigor, anticipation and continuity are the order of the day!
But what do you do when the original service provider is no longer able to keep up? A new development service is inevitable, and that's where Le Backyard comes in. We're used to accompanying companies through this delicate transition, and we'll give you the keys to ensuring project continuity and quality.
I. Understanding the technical stack
The technical stack is the set of technologies used to design, develop and run the web or mobile project, from frameworks to databases and third-party services. Knowing it well is the basis for taking over the project's code.
1. Identify the technologies used
The first step is toidentify the technologies that enable the frontend (user interface) and backend(API, database, payment services, etc.) to function.
By clearly listing all the components of the technical stack, the new service provider will be able to check whether he has the necessary knowledge to work with these technologies and, consequently, assess whether or not taking over development services is realistic.
Sidebar: The importance of open source
Right from the design phase, selecting open-source technologies is essential, since they are widely distributed and documented, and therefore mastered by most service providers. Conversely, development using proprietary technologies will pose problems.
2. The "go / no go" phase
The go / no go phase is central and systematic for an agency like Le Backyard. Indeed, our experts evaluate the technical feasibility before committing to a takeover.
To do this, they validate a number of points:
- Are we familiar with the technical stack used?
- Is the project sufficiently documented?
- Will the technical base still be relevant in the short and medium term?
Of course, the list of unavoidable questions is never set in stone, and evolves with the project in question.
If the responses are favorable, our team moves on to the next stage. If not, there are two options: a partial redesign (frontend or backend), or a complete redesign if the customer opts for the latter.
II. Transmission of deliverables
Once the new service provider has confirmed that it is capable of taking over the project, the customer must pass on the deliverables in its possession.
1. Signing a confidentiality agreement
Before any code or access is transferred, Le Backyard draws up a confidentiality statement based on the information obtained to date. This document also protects the sensitive data that the customer is about to pass on to the new service provider.
2. Code access
In order for the new service provider to have access to the code, it is transmitted via platforms such as GitHubwhich make it easy and secure to retrieve the entire code.
The customer must also provide all available technical documentation , even if it's sketchy, and authorize access to production and databases.
III. Technical audit phase
To make sure that Le Backyard is able to continue with the project, we carry out an express 2-3-day technical audit for a fee.
1. Check project foundations
Before embarking on a project of this scale, it's essential to carry out an in-depth analysis of the existing situation. That's why Le Backyard starts every rework with a short technical audit of your web application or mobile application, which enables us to assess the following elements:
- project foundations and structure ;
- code quality ;
- compliance with best practices ;
- dependencies, libraries, external APIs, etc ;
- existing documentation
This study of the existing product also enables us to detect any errors or problems.
Identify critical points
Our experts take advantage of this audit to identify the disadvantages and divide them into two categories:
- critical points (major bugs, urgent updates, major errors, etc.) for which corrective action must be taken as soon as possible;
- non-critical points (improvements, code clean-up, dependency updates, etc.), which are naturally included in the project's evolution.
This technical audit forms the basis of a clear, prioritized action plan.
IV. Action plan and cost estimate
By estimating the critical and non-critical points, it is possible to draw up a comprehensive action plan for project recovery, including :
- urgent code corrections to be made as soon as possible;
- the new code goes online.
But the work doesn't stop there, the action plan also takes into account the evolutions of this new code as the project grows or evolves. This may involve functional evolutions, performance optimization, RGPD compliance, etc., which are to be included over the medium term.
This action plan is of course coupled with a costed estimate for each stage. This work is normally carried out on a fixed-price basis (if the objectives are clear) or on a time-and-materials basis (with ongoing follow-up via corrective tickets).
In conclusion, the recovery of a development service is an important and delicate operation, which needs to be structured and rigorous. This guarantees the product's longevity without having to start from scratch, which can be very costly for the customer.
Over the past few years, Le Backyard has taken on numerous projects in a wide variety of sectors. If you'd like to entrust your project to us, you're in good hands. Contact us here!
.jpg)
.jpg)
