Planning elements

Planning elements

The planning elements Test sessions and Meetings are described in their topics.

Projects

The project is the primary entity of ProjeQtOr.

It is also the top-level of visibility, depending on profiles.

Sub-projects

  • You can also define sub-projects on a project.
  • Then, the project may not be real projects, but just organizational breakdown corresponding to the organization.

Fix planning

  • When box “fix planning” is checked, the project scheduling won’t be remade.
  • This will avoid change on planned values.

Under construction

  • When a project is under construction, no automatic email is sent for the elements of the project.
  • A project can be under construction as long as it isn’t stated (set to handled status).

Manual indicators

  • Fields: Health status, Quality level, Trend and Overall progress are manual indicators.
  • They allow define visual way the general health, conformity, trend and progress of the project.
  • Some manual indicators are displayed on the Today screen.

Special fields

  • The value of the fields the Project name, Sponsor, Project code and Contract code can be used as the substitute value of special fields.
  • See: Special fields

Monitoring indicator

Project reserve

  • Project reserve is an amount reserved based on identifying risks and opportunities.
  • Calculated from contingency reserve of risks minus potential gain of opportunities.
  • ProjeQtOr uses a technique as “Expected monetary value (EMV)” to convert risks and opportunities into an amount.
  • The amount of project reserve will be added to remaining amount.
  • See: Risks and Opportunities

Section: Description

Field Description
Id Unique Id for the project.
Name Short name of the project.
Type Type of project.
Organization The organization of the project.
Customer The customer of the project.
Bill contact Billing contact.
Project code Code of the project.
Contract code Code of the contract of the project.
Customer code Code of the customer of the project.
Is sub-project of Name of the top project if this project is a sub-project.
Sponsor Name of the sponsor of the project.
Manager Name of the resource who manages the project.
Color Color of the project, to be displayed in some reports.
Status Actual status of the project.
Health status Global health status of the project.
Quality level Estimation of quality level of project (result of audits).
Trend Trend of global project health.
Overall progress Overall progress to be selected in a defined list.
Fix planning Box checked indicates the planning of the project is frozen, and its sub-projects.
Under construction Box checked indicates the project is under construction.
Done Box checked indicates the project is finished.
Closed Box checked indicates the project is archived.
Cancelled Box checked indicates the project is cancelled.
Description Complete description of the project.
Objectives Objectives of the project.

* Required field

Field: Customer

  • The value of the field is used in the Quotations, Orders and Bills concerned with the project.

Field: Bill contact

  • The value of the field is used in Bills concerned with the project.

Section: Sub projects

  • List of sub-projects under for the project.

Activities

An activity is a kind of task that must be planned, or that regroups other activities.

An activity can be:

  • Planned tasks.
  • Change requests.
  • Phases.
  • Deliveries.
  • Versions or releases.

Assigned resources

  • Resources are assigned to activities.
  • During an assignation, some work is initially planned on this activity for the resource.

Real work allocation

  • For a resource, assigned activities are tasks in which he can entry the real work.

Activities regroupment

  • Activities can have parents to regroup activities.
  • So a WBS (work breakdown structure number) is calculated for the activities.
  • Activities can be sorted inside their parent activity, on the Gantt planning view, using drag and drop.
  • Parent activity must belong to the same project.

Work on tickets

  • Tickets can be linked to an activity (task).
  • Work on tickets will be included in the activity.
  • More detail, see: Tickets screen.

Assignment of resources to task

  • Resources who will work on the ticket doesn’t need to be assigned to linked activity before.
  • The assignment will be automatically created once that resource has entered the working time (real work) in the ticket.
  • The assigned task and the sum of working time entries by resource in tickets will be available in its timesheet.

Monitoring indicator

Section: Description

Field Description
Id Unique Id for the activity.
Name Short description of the activity.
Activity type Type of activity.
Project The project concerned by the activity.
External reference External reference of the activity.
Requestor Contact at the origin of the activity.
Origin Element which is the origin of the activity.
Description Complete description of the activity.

* Required field

Section: Treatment

Field Description
Parent activity Parent activity for grouping purpose.
Status Actual status of the activity.
Responsible Resource who is responsible for the activity.
Handled Box checked indicates the activity is taken over.
Done Box checked indicates the activity has been treated.
Closed Box checked indicates the activity is archived.
Cancelled Box checked indicates the activity is cancelled.
Target version The target version of the product allocated in delivery of the activity.
Result Complete description of the treatment done on the activity.

* Required field

Field: Target version

  • Contains the list of product versions linked to the project.
  • More detail, see: Product concept

Milestones

A milestone is a flag in the planning, to point out key dates.

Milestones are commonly used to check delivery dates.

They can also be used to highlight the transition from one phase to the next.

ProjeQtOr offers two types of milestone:

Floating milestone

  • This milestone will automatically move to take into account dependencies.

Fixed milestone

  • This milestone is fixed in the planning, not taking into account predecessor dependencies.
  • This kind of milestone is interesting, for instance to set-up start date for some tasks.
  • Fixed date is set by validated date.

Monitoring indicator

Section: Description

Field Description
Id Unique Id for the milestone.
Name Short description of the milestone.
Milestone type Type of milestone.
Project The project concerned by the milestone.
Origin Element which is the origin of the milestone.
Description Long description of the milestone.

* Required field

Section: Treatment

Field Description
Parent activity Parent activity for grouping purpose.
Status Actual status of the milestone.
Responsible Resource who is responsible for the milestone.
Handled Box checked indicates the milestone is taken over.
Done Box checked indicates the milestone has been treated.
Closed Box checked indicates the milestone is archived.
Cancelled Box checked indicates the milestone is cancelled.
Target version The target version of the product allocated in delivery of the milestone.
Result Complete description of the treatment done on the milestone.

* Required field

Field: Target version

  • Contains the list of product versions linked to the project.
  • More detail, see: Product concept