|
|||||||
| . | Home | Products | Advertising | News | About | Contact | Legal |
Google Search:
|
jxProject 2.5.0.2 - Gantt User Documentation June 23, 2007
Gantt: If you are familiar with using other project management software packages then jxProject should have a look and feel that is familiar to you. The software is based on the Gantt Chart which was developed by Henry Gantt (1861-1919) to be used for scheduling multiple overlapping tasks over a time period. jxProject allows you to build dependencies between tasks and it rebalances the project plan to reflect those dependencies. Dependencies are often/usually referred to as constraints. Main components of the jxProject Gantt interface:
Figure 1: The Gantt Interface
The labels used in describing the basic components of the jxProject interface in Figure 1 will be used consistently throughout this document. Elements of the Gantt Chart: While we have Figure 1 starring at us lets cover a few basics. The tree table and the Gantt Chart are closely related and only serve as alternative visual representations of the exact same data. Each row in the table represents the data in the same row in the Gantt Chart to the right. The data which fuels these interfaces is a collection of user defined tasks. These user defined tasks have relationships between each other which are also user defined. That’s really all there is to this tool. Sounds simple enough eh? However, because of the variety of relationships you can define between tasks, project plans often become amazingly complex. But no matter how complex the project plan gets, it is simply a group of tasks and the relationships between them. Now a few definitions: 1. Task: This is the “atomic element” of a project plan. It has a start date, duration and an end date. These are represented on the chart as black outlined rectangles with a fine grained blue and white checkerboard fill color. 2. Summary Task: This is a “roll-up” of tasks which are considered “children” of these tasks. A summary task must have at least one child task. A summary task and its child task have a hierarchical relationship. These are represented on the chart as solid black polygons which are largely rectangular. 3. Link: This defines a direct relationship between exactly two tasks where either or both tasks can be summary tasks. One task of the link is called a predecessor task and the other link is called the successor task. These are represented on the chart as solid black lines between the two tasks with the arrow head pointing at the successor task. Resource User links are brown lines with “crows feet” on the ends, no arrow heads. 4. Arbitrary Constraint: This is a date constraint which appears as green/orange arrows in the chart. An arbitrary constraint will dictate that a task must start after or finish after a specific date. The finish after constraints are single headed green arrows where start after constraints are double headed green arrows. There are also must start before and finish before arbitrary constraints. 5. Predecessor Task: Acts as the primary or driver task in resolving the relationship between itself and its successor task. 6. Successor Task: Acts as the subordinate task in the linked relationship between two tasks.
Elements of the Tree Table: A tree table is what you get when you cross a traditional GUI table with a traditional GUI tree. It’s a table with expandable collapsible nodes. The furthest left column of the tree table is the “key” field and it can never be scrolled out of view. Every other column in the table can be scrolled and the order of the columns can be changed by dragging the columns into different positions using the column headers. Now a few definitions: 1. Key: Each task has a key value which is unique to all other tasks. The key values are assigned by the software but the user can renumber them right clicking on the header. You can increase and decrease the table row height by pressing the (keyboard shift key and the right mouse key on the row table header) simultaneously and dragging it towards the bottom to increase the row height and towards the top to decrease the row height. 2. Task Name: This is the name of the task or description of the task. 3. Resources: These are the names of people assigned to this task. If this field is blank then the “default resource” is assigned to the task. The first resource in the list is the “span resource”, so if a task is “span” driven, then the span resource schedule is what is used to calculate the start time and duration of the task. 4.
5. Span: This is the aggregated work hours of the span resource during the duration of the task. A triangle in the upper left corner of this field indicates that span is the driving or constant parameter in the task and that work and duration are derived from the the span value. For span driven tasks: Duration = the absolute amount of time the task must endure in order to satisfy the required span work time. Work = the aggregated work hours of all of the assigned resources during the duration of the task. The span resource is the first resource assigned to the task and is the first resource name in the list of resources. The span of summary tasks cannot be set by the user and is an aggregate of all is child task span values. NOTE: The custom schedule and time zone of each resource is used in these calculations. Also, these values are adjusted to represent Full Time Equivalent (FTE) values. Example: A span driven task would be one where the addition of resources would NOT result in the task taking less time to complete. If the task were, “Have a meeting to review requirements”, adding more resources to the meeting would not make the meeting any shorter, but does increase the amount of work spent on the meeting. 6. Duration: This value is defined as finish date – start date. A triangle in the upper left corner of this field indicates that duration is the driving or constant parameter in the task and that work and span are derived from the duration value. For duration driven tasks: Work = the aggregated work hours of all of the assigned resources during the duration of the task. Span = the aggregated work hours of only the span resource during the duration of the task. The span resource is the first resource assigned to the task and is the first resource name in the list of resources. NOTE: The custom schedule and time zone of each resource is used in these calculations. FTE values are not utilized in the display or edit of duration values. The durations of summary tasks cannot be set by the user. Example: A duration driven task would be one where the task takes an absolute amount of time regardless of resources. If the task were, “Wait 36 hours for paint to dry”, a duration driver is the way to go. 7. % Complete: Has a range of 0 to 100. It is used to indicate the amount of the task that is complete. For summary tasks the % complete is aggregated from its child tasks and is weighted by the amount of work the child task represents. 8. Resources: These are the first names of people assigned to this task. If the field is blank then the “default resource” is invisibly assigned to the task. 9. Rank: This is used to determine which task gets first priority to the Resources which are assigned to it. If two tasks have the same Resource assigned to them, the task with the lower Rank value will be scheduled first. The Rank of a task is determined by its row position and its constraints. Tasks that are towards the top of the table will tend to get the lower Rank values. A successor task always has a higher Rank value than its predecessor. The Rank value is generated by the constraint solver but there are several tools available to the user to alter the ranking of tasks See the documentation on Resource Leveling for more information. 10. Start: This is the start date of the task. This is an editable field but it is only used to add or change the start after constraint (Arbitrary Constraint) of the task which will be described later in the constraints section. 11. Finish: This is the finish date of the task. This is an editable field but it is only used to add or change the finish after constraint (Arbitrary Constraint) of the task which will be described later in the constraints section. 12. Predecessors: This is a comma delimited field of task keys which are predecessors of this task. This field can be used to add, edit or delete predecessor task links. 13. Successors: This is a comma delimited field of task keys which are successors of this task. This field can be used to add, edit or delete successor task links. 14. Priority: A set of priorities from Lowest to Highest. The priority value does not affect the scheduling of the task. 15. Notes: The notes associated with the task. Best accessed through the task edit dialog. 16. Info: A non-editable field which indicates a problem with the task such as an arbitrary constraint violation. 15. WBS: A non-editable field showing the work breakdown number for the task; (ie. 2.1.4) 16. Driver: A non-editable field indicating a numeric value for the type of scheduling driver for the task, work/duration/span.
Constraint Elements: This is a listing of constraints which affect the scheduling of tasks. The user cannot directly set the start or finish dates of any task; this is done by the constraint solver which is contained within jxProject. The user must define constraints which act upon the task in order to alter the scheduling of a task. 1. Hierarchical: This is the parent/child relationship which exists between a summary task and one or more tasks. A summary task starts at the same time of the earliest start date of its child tasks and ends at the latest finish date of its child tasks. A child task is constrained to be scheduled within the constrained scheduling of its parent/summary task. A summary task can contain millions of child tasks. 2. Links: These define a direct relationship between exactly two tasks where either or both tasks can be summary tasks. One task of the link is called a predecessor task and the other link is called the successor task. A task may have up to 1 billion links. There are four link types: a. Finish to Start (FS) (default): The finish date of the predecessor task pushes the start date of the successor task. b. Finish to Finish (FF): The finish date of the predecessor task pushes the finish date of the successor task. c. Start to Finish (SF): The start date of the predecessor task pushes the finish date of the successor task. d. Start to Start (SS): The start date of the predecessor task pushes the start date of the successor task. e. Resource User (RU): The successor task is constrained to have a rank value that is greater than the predecessor task. f. Pseudo Links (Ra+, Ra-): These are not links, but tools to alter the ranking of tasks. They appear here only for completeness and are discussed in detail in the resource leveling documentation. 4. Rank: The rank of a task determines the priority in which it is scheduled with respect to the resources assigned. The task with the lowest rank value gets resources before any other task. Rank is only relevant when resource leveling is enabled and it serves as the tie breaker in scheduling tasks which share the same resource(s). See the resource leveling documentation for more details. 5. Arbitrary: This constraint is used when the scheduling of a task is determined by constraints which are outside the control of the project. An example would be that you have a set of tasks in your project which depend on the arrival of a piece of equipment. You would put in the arrival date of the equipment as an arbitrary constraint preceding those tasks which depend on the presence of that equipment. A task may have at most one of each kind of arbitrary constraint. There are four types: a. Start After: The task must start after this constraint. b. Finish After: The task must finish after this constraint. c. Start Before: The task must start before this constraint. (Not enforced by constraint solver) d. Finish Before: The task must finish before this constraint. (Not enforced by constraint solver) Note: The start/finish before constraints are not enforced by the solver. An impossible example: Task A must start on Monday and must finish one day later (Tuesday) and has a duration of 10.0 days. It is impossible for the constraint solver to resolve this set of constraints. The task will finish 10.0 days after it starts and an “Error” will appear in the Info column of the Gantt table in indicate that the finish before constraint is being violated. 6. Resources: Tasks are constrained to begin only when at least one of the assigned resources is available to work. If no resource is assigned, the schedule of the “Default Resource” is used to satisfy this constraint. Title Bar:
Menu Bar:
File Menu: · New: Create a new file. · Open…: Open an existing file (*.jxp) · Recent Projects…: Open a dialog showing the last 50 project files opened/saved. · Close: Close the file that is currently open. · Save: Save the currently open file · Save As…: Save the currently open file with a new name. · Import XML: Import a jxProject file which is in XML format. · Export XML: Export the jxProject file in XML format. · Print Preview…: This takes you to the print preview screen and you can configure the printer or print from there. · HTML/images…: This takes you to the image preview screen. From here you can view and alter the size of the images produced when you save the html file. The output is a simple html file utilizing the images of the table and chart. · 1: file:/c/... There will be a listing of up to 4 of the previously accessed files. · Exit: Exit the application
Edit Menu:
View Menu:
Insert Menu:
Tools Menu:
Help Menu:
Upper Tool Bar:
Lower Tool Bar:
Tree Table Interaction: ·
Key:
· Task Name: This is the name or description of the task and you can type anything you like into the field. The expand/collapse icons only appear on summary tasks and you can click on those icons to expand or collapse this task. · Work: The default display unit is hours. Clicking on the work value of a task you will get a “spinner” editor with up and down arrow that allows you to adjust in increments of 0.1. You can also type in your own values without using the arrows if you like. You cannot change the work of a summary task. NOTE: The work/span times are Full Time Equivalent (FTE) adjusted. Example: Lets say an FTE works 8.0 hours per day and the work in “Hours” is 24.0. If you change the work units to “Days” then the value will be 3.0 as it takes 3 FTE days to produce 24 hours of work. · Span: The default display unit is hours. Clicking on the span value of a task you will get a “spinner” editor with up and down arrow that allows you to adjust in increments of 0.1. You can also type in your own values without using the arrows if you like. You cannot change the span of a summary task. NOTE: The work/span times Full Time Equivalent (FTE) adjusted. Example: Lets say an FTE works 8.0 hours per day and the span in “Hours” is 24.0. If you change the span units to “Days” then the value will be 3.0 as it takes 3 FTE days to produce 24 hours of work. · Duration: This default display unit is days. Clicking on the duration of a task you will get a “spinner” editor with up and down arrow that allows you to adjust in increments of 0.1. You can also type in your own values without using the arrows if you like. You cannot change the duration of a summary task. NOTE: The duration time is NOT Full Time Equivalent (FTE) adjusted. Example: Lets say the duration in “Hours” is 24.0. If you change the duration units to “Days” then the value will be 1.0 as there are 24 hours in a day. Gantt Table header context/pop up menu: The Column Visibility option will bring up a dialog where you can see what columns are available and can adjust the visibility, width and order they appear in the table. The Date Format option is only available for columns that require defined date formats such as start and finish dates.
·
Start Date: The date displayed is the start date of the
task. If you edit this field it will create a “start
after” arbitrary constraint for the task.
·
Finish Date: The date displayed is the finish date of
the task. If you edit this field it will create a “finish
after” arbitrary constraint for the task.
· Successors/Predecessors: This is a validating comma delimited field of linked task keys. Default link types which are Finish to Start do not have any character designation but the other 4 links types(see constraints) do have 2 character designators (SS, FF, SF, RU). · Resources: To assign resources to a task via this table you must bring up the resources assignment dialog and drag one or more resources onto the task row to which you want the resource(s) assigned. A resource in the dialog is selected when the entire row is selected. To initiate the drag you must press down the first mouse button on the “key” cell of the selected resource(s) and begin dragging quickly. To delete a resource from a task, double click the resource cell to bring up the editor list of all the resources. Uncheck the check box next to the resource name or set the % spinner to zero which will also delete the resource from this task. The spinner can be used to assign partial resources to tasks.
· Hot Keys/Accelerator Keys: Shift+F10 will bring up the table context menu; Shift+Space will select the entire row for any selected cells; Cntrl+Space will select the entire column for any selected cells; Alt+Shift+I will indent selected tasks; Alt+Shift+O will indent selected tasks. · Dragging and Dropping: Using drag and drop it is possible to move or copy tasks. To initiate a drag, select one or more tasks using the row header to select the entire row. Then press and drag the first mouse button on the “key” field of the selected task(s). Do this quickly so the drag gesture is recognized. Your cursor will change to reflect the type of drag operation that has been initiated. The default drag is a move, if you hold down the control key while initiating the drag, the operation will be a copy. A copy cursor has a “+” sign on it. When tasks are copied, links to tasks that are outside of the group of tasks will be removed from the newly copied tasks. ·
Tree Table Context/PopupMenu:
Assigning Resources to tasks: To assign resources to a task via this table you must bring up the resources assignment dialog and drag one or more resources onto the task row to which you want the resource(s) assigned. A resource in the dialog is selected when the entire row is selected. To initiate the drag you must press down the first mouse button on the “key” cell of the selected resource(s) and begin dragging quickly. If you want to assign one or more resources to multiple tasks in a single step. Highlight only the resource cells in the task table to which you want to assign resources, then drag resources from the Resource Dialog and drop them onto the range of selected resource cells. The resources will be assigned to all of the highlighted tasks. If a task is already linked to one of the resources, the existing relationship will be maintained and not altered. Figure 2: Assigning a resource to a task via Drag and Drop
Figure 3: Resource Table Cell Editor; for resource delete Table Pan Scrolling/Auto scrolling: Pan scrolling the tree table is activated by single clicking on the table with the middle mouse button. The pan scroll will work for any component inside a scroll pane and gives the user the ability to fly over the component. Gantt Chart Interaction: There is not a lot of interactivity in the Gantt Chart but there are some things that you can only do from the Gantt Chart so read closely.
Gantt chart context menu: A right click on the Gantt Chart or Shift+F10 will bring up this context menu.
Edit Task dialog: This dialog is accessed by double clicking the “key” cell of the Gantt Table or double clicking a row/task or item associated with a task in the Gantt Chart.
If the user double clicks on a link in the Gantt Chart, this dialog will pop up and the selected link will be highlighted in the table.
The resource name searches are case insensitive and there are a variety of ways to search. Example: “bob” would match “Bobby” FFF just search first name LLL, just search last name LLL, FFF search last and first name LLL, FFF MMM search last and first name and middle name FFF LLL search first and last name FFF LLL MMM search first and last name and middle name <SP>II just search resource initials; Note: <SP> indicates white space entry <SP>II<SP>I just search resource initials start and ends with; Note: <SP> indicates white space entry ? Return a dialog listing all resources. The user can also type the key # of any task in the the ID column to add a resource. The timeout dialog, shown in the above image, is an informational dialog and has a countdown timer which starts as soon as it is displayed. When the timer expires, reaches zero, the dialog goes away. If you want to hold the dialog, click on the countdown number to stop the countdown, double click on the number to dismiss the dialog.
Schedule Tab: These are options to alter the appearance of the schedule chart.
Resource Assignment Tab: These are options to alter the appearance of the schedule chart in the resource assignment dialog.
Gantt Tab: These are options to alter the appearance of the Gantt chart.
Solver Tab: These are options relating to how the solver resolves constraints:
FTE-Work Tab: These are options to define the work hours of a full time resource:
|
|
|||||
|
|
|||||||