HowToOrganizeEntitiesHierarchically

How to organize requests and tasks hierarchically

In Plandora requests can be structured hierarchically by project leader through the "Show All Request Form". This form contain a grid with all project requests (including on-cascade projects).

The grid contain a column called "Parent", where the leader is able to input a list of requests ids (separated by comma) defining a hierarchy structure. After saving the definitions, the view mode must be changed.

About this feature is important to mention:

1. It is possible to define a request with multiples parents.

2. Normally, a request is closed only after all tasks closing. Using hierarchy requests, the parent request will be closed only after all sub-requests are closed

About tasks, Plandora allow project leaders to create macro-tasks that can encapsulate a group of tasks. A fairly comparation could be the "work package" of a WBS approach.

The leader must create the macro task at "Form Task". The procedure is the same of a common task, except that a macro-task contain no resource or estimated time defined. All macro-tasks created will be available to resources through the "Task Track Form". The resource can freely to link the current task under a macro-task "umbrella".

About this feature is important to mention:

1. A macro-task will be closed after closing of the last "in-progress" sub-task. After that, the macro task will not be displayed at drop down list anymore.

2. The gantt chart will display a macro-task like a visual agregator involving all sub-tasks.

Plandora also allow to create dependency between tasks and address this issue through the "Relationship" grid. This generic grid appears at most of Plandora planning entities (Risks, Occurrences, Requests, etc) and allow the resource or leader to create logical connections between entities.

One of those connections is called "Blocks..." and is used to define which tasks will be blocked by another tasks. While the blocker task are not closed, the affected tasks will be not able to be worked.

The resource (worker) will notice at "My Task" grid, an icon with a padlock image showing that the task cannot be worked because it is waiting for something.

The Plandora workflow engine uses this mechanism to coordinate the order of execution of a group of tasks.