Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

A summary task helps in organizing and managing tasks just like we use folders and sub-folders to organize documents. Summary tasks are constituted of sub tasks and they contain the summarized information associated with those sub tasks, such as work and cost involved in accomplishing those tasks.

Summary tasks have the following implications:

  • A summary task’s start date, finish date and duration are automatically calculated based on its sub tasks and therefore, cannot be entered manually. The start date is the minimum of the start dates of its sub tasks, while the finish date is the maximum of the end dates of its sub tasks.The duration is the max elapsed working days between the start and finish dates.
  • Constraint dates are not applicable for summary tasks.
  • Budget of a summary task is the sum of budgets of all its sub tasks.
  • Estimated Cost of a summary task is the sum of estimated costs of all its sub tasks.
  • Resources assigned to a summary task will not be factored into the estimated cost of the summary task, nor displayed on the RLC
  • The % Complete of a summary task is automatically calculated as the weighted sum of percent complete of all its sub tasks and explained as follows :

    If p is the percentage complete of a task and w is the estimated effort on a task, then:
Percentage complete of a summary task = (w1 x p1 + w2 x p2+...) / (w1 + w2 +...), where 1, 2, 3... are its sub tasks. 

To illustrate it further, let us consider an example :

Task NameEffortDurationAssigned To% Complete
T124h3dJoe[100%]100
T20d2d 0
T316h1dJoe[100%], Mary[100%]100

Using the above formula, the calculation will be done as (24x100 + 16x0 + 16x100) / 24 + 16 + 16 =71%

In the above example, for T2 the work is 0d. For such tasks i.e where effort(w) is 0 as no resources are assigned, effort(w) = duration.

  • When you delete a summary task, Celoxis will automatically delete all its sub tasks.
  • Summary tasks will always be auto-scheduled; even though its child tasks are manually scheduled.
  • No labels