355 | | * We need a way to express WBS relationships, assuming !MasterTickets will be used to express dependencies. If we need more than FS dependencies, we will need to extend !MasterTickets to express dependency type. |
356 | | |
357 | | * !TimingAndEstimation can be the basis of recording estimates. The plugin should be extended to support original and revised estimates, and to store default estimates in the database (rather than have rules to use the default value for tickets with tiny estimates). |
358 | | |
359 | | * We need a new resource plugin to allow describing resources and their availability. This should support notions of normal work hours, holidays, etc. |
360 | | |
361 | | * [#DependencyandDuration Basic scheduling] can be provided based on core Trac tickets, !MasterTickets, and !TimingAndEstimation. (This discounts resource conflicts and availability.) A new Scheduling plugin can build on these plugins (or an interface that hides them), add Start and Finish dates to tickets, and schedule going back from a milestone. |
362 | | |
363 | | * Once a scheduler exists, a simple Gantt chart can be implemented to show dependencies and schedule. (This might even be a revision or refinement of an existing Gantt.) |
| 355 | * We need a way to express WBS relationships, assuming !MasterTickets will be used to express dependencies. |
| 356 | * If we need more than FS dependencies, we will need to extend !MasterTickets to express dependency type. |
| 357 | * Note that there is a [ticket:7812 patch] to TicketImportPlugin that imports WBS relationships. It is known to work with !MasterTickets and Subtickets plugins and may work with others. |
| 358 | |
| 359 | * !TimingAndEstimation can be the basis of recording estimates. |
| 360 | * The plugin should be extended to support original and revised estimates, and to store default estimates in the database or configuration or derive them from history for experience-based scheduling (rather than have rules to use default values for tickets with tiny estimates). |
| 361 | |
| 362 | * A simple Gantt chart can be implemented to show dependencies and schedule based on manually-entered due dates. |
| 363 | * TracJsGanttPlugin provides such a display. |
| 364 | |
| 365 | * [#DependencyandDuration Basic scheduling] can be provided based on core Trac tickets, !MasterTickets, and !TimingAndEstimation. (This discounts resource conflicts and availability.) A new Scheduling plugin can build on these plugins (or an interface that hides them), add Start and Finish dates to tickets, and create an as-late-as-possible schedule working back from a milestone. |
| 366 | |
| 367 | * We need a resource calendar plugin to allow describing resources and their availability. This should support notions of normal work hours, holidays, etc. |