Stocks are used in anticipation of risk. They serve to reduce the risks.

The analysis of these risks consists in defining actions. There are two types of actions:

  • Preventive action aimed at removing the risk or

  • Corrective action that has been earned on the occurrence of a risk


An Activity can be likened to the key stages of the project: it is the skeleton of your project that organizes the main phases of a project

  • They have a start and end date

  • They designed for the planning phases of a project

  • They serve to organize the milestones and tasks of a project

  • They can allocated to a or many resources

  • They can be prioritized and have sub-activities


An administrator is a user with “Administrator” profile. Has a visibility over all the projects.

Agile methods

Agile methods are groups of practices of piloting and realization of projects. They originate from the Agile manifesto, written in 2001, which uses the term ‘agile’ to refer to multiple existing methods


The client is the person on whose behalf the work is carried out. It is the sponsor and the one who bears the financial cost. The client is a natural or legal person, public law or private law


Closed is a micro state in ProjeQtOr

  • Flag to indicate that item is archived.

  • Item will not appear in lists any more

  • You can display them again by checking the box “Show closed items”

  • You can setting their default display in the user’s Parameters


A contact is a person in a business relationship. A contact can be a person in the customer organization. Used as contact person for contracts, sales and billing. Contacts management is performed on Contacts screen.


coordinator is the person who oversees and reports. It corresponds to the accountable in the RACI method In ProjeQTOr, the responsible is the person who works.


cron is a program that allows users of Unix systems to automatically execute scripts, commands or software at a date and time specified in advance, or according to a cycle defined in advance.


It is an English computer acronym for Create, Read, Update, Delete. It designates the four basic operations for data persistence, in particular the storage of information in a database.


A good decision helps move towards the end goal. It is in the general interest, the interest of the greatest number as well as in the interest of the project

a good decision is a suitable solution, put in place with the tools and resources available at a given moment.

  • This field allows to define a description on an item.

  • Depending on the element type, name of field can be different.

See also

GUI behavior

  • It is possible to define that description field is mandatory.

  • The element type screens allow to set this parameter to several elements.

  • More detail, see: Behavior section.


Done is a micro state in ProjeQtOr

  • Flag to indicate that item has been done.

  • Date of done is saved.

  • A result can be specify.

  • It is possible to require a result when the status change to “done”.

External reference
  • This field allows fill free input.

  • It uses to refer information from an external source.

  • External reference value can be put in email message with externalReference special field.

  • More detail, see: Administration


Full Time Equivalent The full-time equivalent (FTE) is a unit of measurement: a workload or more often, a capacity for work or production.

Gantt chart

Description The Gantt chart is a tool used in scheduling and project management and allowing to visualize in time the various tasks composing a project.

It is a representation of a connected graph, evaluated and oriented, which makes it possible to graphically represent the progress of the project

In Progress
  • Flag to indicate that item has been taken into account.

  • Date of handling is saved.

  • This generally means that responsible has been named.

  • Every item has a unique Id, automatically generated on creation.

  • Id is chronologically allocated, for all kind of items (Activity, Ticket).

  • Id is shared for all projects and all types (i.e. incident) of the same kind items (i.e. Ticket).


Any event that is not part of the standard operation of a service and that causes, or may cause, an interruption or decrease in the quality of that service


An issuer is a user who created the item.

See also

Creation information

The issuer name and creation date of an item are displayed in the Creation information zone.

Key Performance Indicator (KPI)

Indispensable to the project manager, an indicator makes it possible to evaluate a situation and to make an adapted decision. Key performance indicators measure the performance of your projects. You choose them together with your team. They must be simple, reliable, easily understandable by all and relevant

If the indicator is green, all is well, you will need to continue the actions in progress to maintain this good result. If the indicator is red, then you must take the necessary corrective action. If the indicator is orange, it should be monitored.

  • Each indicator is associated with a specific goal.

  • An indicator necessarily implies a decision.

  • An indicator is never silent.

  • A relevant indicator must be simple


An objective is a goal to achieve by carrying out different tasks. For example, building a new plant in order to produce more and meet the growing demand. It is essential to precisely define the goal (s) to reach so that you and your team know where you are going. A good goal must be SMART.

  • Determines the element of origin.

  • The origin is used to keep track of events (ex.: order from quote, action from meeting).

  • More detail, see : Origin field.

PERT chart (Program Evaluation and Review Technique)

provides a practical method and means to describe, represent, analyze and logically follow the tasks and the network of tasks to be carried out as part of an action to be undertaken or to be followed. The PERT diagram represents the work schedule by a dependency graph. His network formalism focuses on the interconnection of the tasks to be performed and the calculation of critical paths.

An important difference with the Gantt chart is the conventional time scale of the PERT chart which represents a sequence of tasks and not durations or a calendar


A project is defined as a finite set of activities and actions undertaken in order to meet a defined need within a set timeframe and within the limits of an allocated budget envelope

See: project

Project Leader

A project leader is a resource allocated to a project with a “Project Leader” profile. person responsible for leading a project and managing its smooth running. In general, he leads a team during the duration of the various projects for which he is responsible

Project manager

A project manager is a resource defined as the manager on a project.

See also

Accelerator button

This button allows to set current user is the project manager. More detail, see: Assign to me button.

Project team

All resources allocated to a project.


A quotity is the amount of a quota. This term of right refers to the fraction of a whole, a proportional sum in a share. A quota can be to pay or to collect.


R - Responsible - he realizes A - Accountable - he oversees and reports C - Consulted - he advises I - Informed - he is informed

In projeQtOr the accountable is defined as coordinator

  • Reference is displayed after id, automatically generated on creation.

  • Reference depends on defined format, see under “Format for reference numbering” section in Global Parameters screen.

  • Default format defines a specific numbering format that can provide unique numbering sequence for each project and/or each type of items.


A requestor is a contact. Used to specify the requestor for ticket, activity and requirement. Only contacts allocated to the selected project can be a requestor.


A responsible is a resource in charge of item treatment. Usually, the responsible is set when the status of the item is In progress. Only resources allocated to the selected project can be a responsible.


**GUI behavior**

It is possible to define that responsible field is mandatory on In progress status.

The element type screens allow to set this parameter to several elements.

More detail, see: Behavior section.

Set automatically the responsible

It is possible to set automatically the responsible.

More detail, see: Global parameters

Accelerator button

This button allows to set current user is the responsible.

More detail, see: Assign to me button.

Access rights

It is possible to define a combination of rights to permit access for elements the user is responsible for.

More detail, see: Access modes screen.

  • Human or material resource involved in the projects.

  • It is possible to define the resource availability to the projects.

  • Resources management is performed on the Resource screen.

  • A result is a description of the treatment of an item.

  • Usually, the result is set when the status of the item is done.

See also

GUI behavior

It is possible to define that result field is mandatory on done status.

The element type screens allow to set this parameter to several elements.


The risk is a hazard, an undesirable event whose appearance is not certain, resulting in the possibility that the project does not achieve the objectives of:

  • Completion date

  • Costs

  • Specifications (techniques, quality, performance , reliability …)

  • Others: Image of the company, environment, legal, social …

The risk can put in danger the project, deviations from forecasts the making it unacceptable or totally unacceptable. We distinguished the risks exogenous (external at now ; suppliers, evolution regulation, political, social, meteorology…)


The Quality approach consists in finding the match between the answer to the needs of the project, the correct expression of these needs by adequate specifications which go through a careful listening of the customer, and a realization answering the expression of the needs.

  • User is a person who logs into the application.

  • User profile define general access rights. But it does not necessarily give access to project data.

  • Users management is performed on the Users screen.


A service level agreement (SLA) is a contract between a service provider and its customers that documents the services that the provider will provide and defines the service standards that the provider is required to meet.


it is an acronym or mnemonic device that stands for ‘Specific, Measurable, Acceptable, Realistic and Temporally Defined’. These terms apply mainly to the determination of the most suitable objectives in order to complete a given project. Setting appropriate targets will help accelerate project completion and improve its chances of success.

  • The status determines the life cycle of items.

  • It defines the progress of the treatment of the item.

  • Item is linked to a element type, element type is linked to a workflow.

  • A workflow defines the possibility to go from one status to another one, more detail, see: Workflow.


Ticketing is an anomaly tracking system : bugs, incidents, problems, requests…

  • Work Breakdown Structure.

  • Hierarchical position of the element in the global planning.

  • WBS also defines the index of an item in the WBS structure. This index is calculated like paragraphs in a word document.

  • Assigned: The work initially planned for this resource to the task.

  • Left: Assigned Work – Real Work

  • Real: Sum of work done by this resource to the task.

  • reassessed: Real Work + Left Work


Except for some planning modes, the planning does not take into account the validated load but that affected.


A workflow is the representation of a series of tasks or operations carried out by a person, a group of people, an organization, etc.

The term flow refers to the passage of an element, from one stage to another.