To the content.
 

TaskJuggler Examples

The examples on this page can give you a first impression of TaskJuggler. They show some basic and some more advanced features. Both the project file as well as the resulting reports are presented. All examples can also be found in the source tarball on the download page.

Example 1: A First Project

The first example is a quick tour of many taskjuggler features. This example is also featured in the TaskJuggler tutorial. It uses all the basic features you need in almost every project. But it also uses many advanced features to show-off TaskJuggler. So don't be scared if all the keywords overwhelm you at first glance.

TaskJuggler Project File Project file for the Accounting Software project
TaskJuggler Project File HTML report that provides an overview of the project tasks
TaskJuggler Project File Printed report that provides an overview of the project status
TaskJuggler Project File Printed Gantt Chart report
TaskJuggler Project File Printed report that shows the resource allocations

Example 2: Shift Schedules

This example shows how TaskJuggler can be used to plan the shift schedule of a team of System Administrators for the next couple of weeks. This is not at all a typical use case for a project management software, but it shows how powerful TaskJuggler really is.

TaskJuggler Project File Project file for the shift schedule
TaskJuggler Project File HTML report that shows the allocations for June
TaskJuggler Project File HTML report that shows the schedules for each team member
TaskJuggler Project File HTML report that shows the task coverage for June

Example 3: A big project

This example shows how to split big projects into smaller sub projects but still have cross dependencies. This idea is to export certain tasks as fixed tasks from one project1 and include them in the other project2. So project2 can reference tasks from project1 without knowing all the details and without the need to combine both project into one mega project.

Project1 and Project2 share a common resource pool. The resource allocations can be included in the exported files, but the project part that is scheduled first, always gets it's resources first. The including project then has to live with the remaining free slots. With good project and resource partitioning this should be no problem. If you can't take that route, you have to take the mega project approach.

See the Interface source file of project 1 which is included in the Project 2 Sourcefile.