Planning elements

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

Project

The project is the primary entity of ProjeQtOr.

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

Sub-projects

  • You can define sub-projects on any project and this unlimited.

  • On the parent project screen, you can view the children in the subproject section.

  • Then, the projects may not be real projects, but just organizational breakdown corresponding to an organization.

Project type

There are 3 types of projects which are not managed in the same way.

  • Operational projects for work planning,

  • Administrative projects for recording unavailability

  • Template projects which will serve as models to be recovered.

See: project type

Fix planning

  • When the “correct planning” box is checked, the project planning will not be recalculated.

  • This avoids modifying the expected values.

  • Planning will always be the same no matter what you do on other projects.

Warning

This may lead to dependencies unconsistancies

Non extendable project

When project perimeter is fixed you can’t:

  • add new elements to this project

  • delete elements from this project

  • move elements to or from this project

Under construction

  • When a project is under construction, no automatic emails will be sent, no notifications or alerts will be generated for the project elements.

  • A project can be under construction as long as it isn’t stated. Set to In progress status.

  • The resources don’t see it on timesheet.

Exclude from global plan

  • Do not show the not plannable items for this project on the global planning view.

  • This means that only standard planning items will be displayed excluding:

Validated work treatment

Activates treatment of the validated work based on the sum of the work of the project orders otherwise it will be calculated on the sum of the validated work of the activities.

Manual indicators

Manual indicator on the Today screen

Manual indicator 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

Do not start project before Validated Start Date

  • The schedule should only start from this date, as if there was a fixed milestone preceding the project.

  • Resources cannot be charged to the project before the specified date (as with a project under construction).

  • This option must be enabled in the global parameters.

Project reserve

  • Project reserve is an amount reserved based on identifying Risks and Opportunity.

  • 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.

Section Description

Required fields Required File legend

Field

Description

Id

Unique Id for the project.

Required File Name

Short name of the project.

Required File 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.

Description

Complete description of the project.

Objectives

Objectives of the project.

Section treatment

Required fields Required File legend

Field

Description

Required File 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.

Non extendable project

When project perimeter is fixed you can’t addor delete elements to this project, move elements to or from this project.

Under construction

Box checked indicates the project is under construction.

Exclude from global plan

Do not show the not plannable items for this project on the global planning view. This means that only standard planning items will be displayed excluding actions, decisions, deliveries.

Validated work treatment

Activates treatment of the validated work based on the sum of the work of the project orders otherwise it will be calculated on the sum of the validated work of the activities.

In progress

Box checked indicates the project is begun.

Done

Box checked indicates the project is finished.

Closed

Box checked indicates the project is archived.

Cancelled

Box checked indicates the project is cancelled.

Activity

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

Parent activities

  • Activities can have parents to regroup activities or planned tasks.

  • Activities can be sorted inside their parent activity, on the Gantt planning view, using drag and drop in the list area.

  • Parent activity must belong to the same project.

  • When a parent activity contains an assignment with a workload then the planning mode applied does not correspond to any of those proposed in the list of planning modes.

  • On a parent activity the planning mode is no longer displayed.

    planning example

    Example with a parent activity with no load and 2 sub-activities with 10 days of load for each of the resources (analyst 1 and analyst 2).

    In this case, the parent activity is the result of the sub-activities that compose it.

    Mother activity without workload

    Mother activity without workload

    If workload is entered for a resource on a parent activity, and this resource is also scheduled on child activities, then the total of this workload will be displayed on the parent activity for this resource.

    Mother activity with workload

    Mother activity with workload

    The dates and durations section display the result

    Dates and durations section on parent activity

    Dates and durations section on parent activity

    The dates and duration section of the activity shows the overall load for a resource.

    20 workload days = 10 workload days for Analyst A for parent activity + 10 workload days for Analyst A for activity A.

    The mother activity, even if it has priority in relation to its position in the WBS, will distribute the workload assigned for the resource after the workload on the sub-activities.

    the load of the mother activity is planned after the sub-activities

    the load of the mother activity is planned after the sub-activities

Activity planning: work on tickets

  • Tickets can be linked to an activity (task).

  • Work on tickets will be included in the activity.

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.

Fix planning

  • When box “fix planning” is checked, the activity scheduling won’t be remade.

  • This will avoid change on planned values.

  • The planning will always be the same whatever you do on other projects.

Warning

This may lead to dependencies unconsistancies

Filter on list

Ability to filter activities by data or type, for instance by assigned resources

Monitoring indicator

Section Description

Required fields Required File legend

Field

Description

Id

Unique Id for the activity.

Required File Name

Short description of the activity.

Required File Activity type

Type of activity.

Required File 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.

Section Treatment

Required fields Required File legend

Field

Description

Parent activity

Parent activity for grouping purpose.

Required File Status

Actual status of the activity.

Responsible

Resource who is responsible for the activity.

In progress

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.

Milestone

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

Required fields Required File legend

Field

Description

Id

Unique Id for the milestone.

Required File Name

Short description of the milestone.

Required File Milestone type**

Type of milestone.

Required File Project

The project concerned by the milestone.

Origin

Element which is the origin of the milestone.

Description

Long description of the milestone.

Section Treatment

Required fields Required File legend

Field

Description

Parent activity

Parent activity for grouping purpose.

Required File Status

Actual status of the milestone.

Responsible

Resource who is responsible for the milestone.

In progress

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.