Our methodology
1. PREPARATION
A good project is a well-prepared and well-supervised project in which all the players are equally involved.
That's why we ask you to provide a certain number of documents in advance, which will be needed to ensure the best possible service.
Specifications
This is the main document, the one that provides us with all the functionalities of your project, as well as as as many details as possible about the expected theoretical workflow.
We can provide you with advice and clarification on the technical consequences of your choices, but it's up to you to determine what the package should do!
Wireframes
Zonings or mock-ups are also useful for giving concrete expression to your desires, and enabling a better dialogue about the functionalities and general ergonomics of your project.
There is a plethora of tools for creating zonings, such as Wireframe.cc or Framebox.org.
If you prefer, don't hesitate to contact us, and we'll put you in touch with a web designer you can trust to help you with this process.
Site tree structure
The tree structure of your site will help you to define the scope of your project, the number of pages and elements you consider necessary for the smooth running of your digital communication tool.
Contents
It's by working on the content of your site and the message you want to get across to your customers that your targets and objectives will be defined. It's worth noting that writing and validating your content takes time, and we can guide you through the process.
The more precise you are, the more precise our work will be!
2. PROJECT PROGRESS
This is where the magic happens! Using the documents supplied and validated during the first stage, we will carry out every aspect of your project.
Depending on the scope of your project, it may be broken down into several batches, each of which will be validated individually. The development and validation stages will then be repeated as many times as there are batches in your project, until the final validation.
Turning your ideas into lines of code takes time, and everyone is enthusiastic about seeing their project progress.
In this way, a development version can be put in place and made accessible to everyone involved.
As well as commenting on our work for future development, we make available all the documents necessary for the smooth running and sustainability of the project.
3. FEEDBACK & VALIDATION
At the end of our work, it's up to you to validate the conformity between what was planned and what was developed.
Let's be realistic, however: the context in which a project is carried out is bound to change, and the specifications initially envisaged may be modified accordingly as development progresses.
We record every difference and compromise so that we can discuss them together during development or afterwards. In this way, we determine whether the element can be modified immediately or whether it needs to be included as an appendix to the project.
Once all the feedback has been validated, the project is nearing completion and all that's left to do is train you in the tool and then deploy it!
4. TRAINING & ONLINE
Depending on your project, you may also have access to a back-office where you can adjust the content of the site once it's online.
Depending on your affinity with IT in general and the nature of your project, we plan a training session ranging from 1 hour to one day with all the players involved.
A user manual will be provided prior to the training, to introduce you to the administrator panel and enable you to get a better grasp of the training, focusing on more specific points.
At the end of the training, we will work together to put the project into production.
A backup of the online date is made and sent to you, along with a backup of the existing system.
5. FOLLOW-UP & MAINTENANCE
At the end of each project, we remain available for a period of one month to resolve any errors that may have slipped through the cracks of testing and validation.
However, this is limited to errors that correspond to the initial documents and the changes requested during the project.
As a project is likely to evolve over time, it is also possible to schedule maintenance hours (TMA), which are purchased in advance and enable the project to evolve according to your needs.
Each request is then treated as a mini-project, with a request, development, validations and feedback, then put online. The hours are then deducted from your total and we warn you when you don't have much time left.
You are then free to renew the contract or not, as we do not schedule any tacit renewal or expiry of the hours purchased.