The TaskJuggler User Manual

Project Management beyond Gantt Chart Drawing

<< efficiency << Table Of Contents >> effortdone >>

Keyword effort


Specifies the effort needed to complete the task. An effort of 6d (6 resource-days) can be done with 2 full-time resources in 3 working days. The task will not finish before the allocated resources have contributed the specified effort. Hence the duration of the task will depend on the availability of the allocated resources. The specified effort value must be at least as large as the timingresolution.

WARNING: In almost all real world projects effort is not the product of time and resources. This is only true if the task can be partitioned without adding any overhead. For more information about this read The Mythical Man-Month by Frederick P. Brooks, Jr.

Tasks may not have subtasks if this attribute is used. Setting this attribute will reset the duration and length attributes. A task with an effort value cannot be a milestone.

Syntax effort <value> (min | h | d | w | m | y)
Arguments value
A floating point or integer number
Context task, supplement (task)
See also duration, length

project "Duration Example" 2007-06-06 - 2007-06-26 {
  timezone "America/Denver"

resource tux "Tux"

task t "Enclosing" {
  start 2007-06-06
  task durationTask "Duration Task" {
    # This task is 10 calendar days long.
    duration 10d

  task intervalTask "Interval Task" {
    # This task is similar to the durationTask. Instead of a start
    # date and a duration it has a fixed start and end date.
    end 2007-06-17

  task lengthTask "Length Task" {
    # This task 10 working days long. So about 12 calendar days.
    length 10d

  task effortTask "Effort Task" {
    # Tux will need 10 days to complete this task.
    effort 10d
    allocate tux

<< efficiency << Table Of Contents >> effortdone >>

Copyright (c) 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014 by Chris Schlaeger <>.TaskJuggler is a trademark of Chris Schlaeger.