Information systems consulting

Qualiente can act as project owner (MOA) and/or project manager (MOE).

With over 10 years' experience working with major accounts (GDF SUEZ, Thomson Multimedia, Bouygues Telecom...), we help our customers to effectively manage a project to create or upgrade an information system.


The specifications help define the criteria for selecting the service provider, and serve as a commitment by the supplier to implement the technical specifications and associated schedule (their content being incorporated into the contract or agreement signed by the two parties).

It is also used, in the form of an acceptance specification, to assess the match between the technical implementation and the needs expressed.

80% of problems originate in the specification phase!

Qualiente offers its customers the opportunity to manage the drafting of specifications for an IT project, by gathering the necessary information from the company's various departments.

Example of a specification summary
  • keyboard_arrow_rightCompany overview
  • keyboard_arrow_rightGenesis of the request
  • keyboard_arrow_rightMacroscopic customer needs
  • keyboard_arrow_rightProject objectives
  • keyboard_arrow_rightElements of benchmarking and competitive intelligence
  • keyboard_arrow_rightProject deliverables
  • keyboard_arrow_rightCorrective and evolutionary maintenance
  • keyboard_arrow_rightCopyright management
  • keyboard_arrow_rightCustomer expectations and commitments to the service provider
  • keyboard_arrow_rightPlanning elements (pre-sales, project, deployment)

In addition to the techniques involved in drawing up specifications, a good knowledge of the market and the service providers involved will enable us to draw up a relevant document and, above all, prevent cost overruns. We take on the role of project manager, and our common objective is to detail your needs clearly (everything that's obvious should be written down!).

If you'd like advice on how to write your document independently, Qualiente also offers a training course on writing specifications.


The role of IT project management assistant (IT PMA) is defined as the intermediary between a customer and the service provider in charge of implementing a software and/or infrastructure solution.

This expertise enables us to understand the technical stakes and to manage the project management, while at the same time relaying information in a comprehensible way to the project owner.

Don't try to learn the best practices of a support function!

A wide range of skills are required: project methodology (V-cycle or agile method), understanding of user issues (empathy), technical skills, analytical and synthesis skills, interpersonal and writing skills, change management...

Examples of IS project management assignments
  • keyboard_arrow_rightFeasibility study and costing of a solution
  • keyboard_arrow_rightDrafting of specifications (expression of needs)
  • keyboard_arrow_rightFunctional design (user path, database)
  • keyboard_arrow_rightMonitoring of contractor's work (development)
  • keyboard_arrow_rightQuality, cost and deadline management
  • keyboard_arrow_rightOrganization of user tests (functional acceptance)
  • keyboard_arrow_rightDefinition of norms and standards for new business processes
  • keyboard_arrow_rightDrafting a user guide
  • keyboard_arrow_rightPreparing training sessions
  • keyboard_arrow_rightAnalysis and monitoring of project risks

Functional recipe

The user testing phase of an IT project, known as functional acceptance testing, requires a rigorous methodology. The more precise the initial document, the easier it will be to identify any anomalies or changes during testing.

Functional acceptance is often reduced to a much too short timeframe, in view of the delays incurred in the preceding stages. That's why Qualiente offers its customers a rigorous approach to user testing, in line with the deadline and the associated human resources.

The main quality of a good tester is to have an eye outside the company!
Examples of support documents for functional acceptance
  • keyboard_arrow_rightFunctional recipe book
  • keyboard_arrow_rightUser test scenarios
  • keyboard_arrow_rightCreating test sets
  • keyboard_arrow_rightDesigning specific minutes