3 - Development process

Building the foundations of your success.

The same attention to details is given to the development process as it was during the previous phase. Our clients appreciate the fact that we use standard conventions for good programming style and all our code is documented.
Your site is developed on one of our servers in-house. You also have access to your own version published on one of our external test servers so you can review the work at your own pace. You can watch the process of the development and participate in testing.

Communication during the development process.

Just as our clients enjoy the online collaboration tool used during the design phase, they appreciate our specific tool for the development phase.
You can follow the development progress in our client portal at any time.

Each member of your team will be given user access:

image here

Once logged in, you will see the list of outsanding work:
The detailed page for each ticket looks like this:

image here

For any given ticket, you can add comments, attach files and see all the vital information related to the issue, including:
Who raised it.
Who is working on it at Inmeres.
The creation date.
The due date.

Tools used during the development process.

Our clients believe it is important to work in a controlled environment: Do you know your suppliers backup strategy? What about revision control system?
Our clients rely on us using all those tools tp deliver quality projects on time.

Backup strategy.

It is really important for our clients to know that all our machines are backup every night to a central NAS (Network Area Storage) in our office. As a double protection, all our work is also stored online as added security.

Revision control system.

Our clients let us know that they wouldn’t want to work with a supplier who doesn’t use a Revision control system at the heart of their project management process.
A revision control system provides the ability to wrap up all the files associated with a project and manage the changes over time. In essence acting like a time machine, a revision control system allows the developer to take the system back to the state it was in just before a problem occurs.
Revision control system are also very useful in a multiple developers scenario. When John and Rob are both working on the same file, the control system will either merge their changes or notify them of overlapping changes that need to be sorted out manually. In either case, this is much more helpful than one of the two developers losing all their work, quite possibily without even realising it.

Our clients are reassured that we have a complete record of all the important changes to the files right there at our fingertips.
On our oldest project we have more than 1,500 “revisions” of the files and we can roll back to any given file as it was in 2002!

Our clients made perferctly clear how important Revision control system is to them. If we had to keep only one of the tools we are using on a daily basis it would be this one.

NEXT: