### The TaskJuggler User Manual

Project Management beyond Gantt Chart Drawing

<< scale (column) << | Table Of Contents | >> scenario (ical) >>

Keyword | scenario

Purpose

Defines a new project scenario. By default, the project has only one scenario called `plan`. To do plan vs. actual comparisons or to do a what-if-analysis, you can define a set of scenarios. There can only be one top-level scenario. Additional scenarios are either derived from this top-level scenario or other scenarios.

Each nested scenario is a variation of the enclosing scenario. All scenarios share the same set of properties (task, resources, etc.) but the attributes that are listed as scenario specific may differ between the various scenarios. A nested scenario uses all attributes from the enclosing scenario unless the user has specified a different value for this attribute.

By default, the scheduler assigns resources to task beginning with the project start date. If the scenario is switched to projection mode, no assignments will be made prior to the current date or the date specified by now. In this case, TaskJuggler assumes, that all assignements prior to the current date have been provided by booking.task statements.

Syntax | `scenario <id> <name> [{ <attributes> }]`
Arguments | id [ID] | The ID of the scenario
name [STRING] | The name of the scenario
Context | project, scenario

Attributes | Name | Scen. spec. | Inh. fm. Global | Inh. fm. Parent
active |  |  | x
scenario |  |  |

<< scale (column) << | Table Of Contents | >> scenario (ical) >>

Copyright (c) 2006, 2007, 2008, 2009, 2010, 2011, 2012 by Chris Schlaeger <chris@linux.com>.TaskJuggler is a trademark of Chris Schlaeger.