Changes between Version 47 and Version 48 of ProjectManagementIdeas

Timestamp:

May 3, 2009, 9:46:45 PM (15 years ago)

Author:

Chris Nelson

Comment:

Refine roadmap

ProjectManagementIdeas

@@ -312 +312 @@
 There seems to be a consensus that grandiose project management features for Trac should be implemented with a combination of plugins which provide useful functionality on their own.  The following plan assumes that approach.
 
- * Basic scheduling can be provided based on core Trac ticket, !MasterTickets, and !TimingAndEstimation if we discount 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.
-
-----
-
-= Development Plan =
-
- 1. Fork !MasterTickets as !TicketDep (or something) and add ''composed of''/''part of'' dependencies and [http://trac.edgewall.org/wiki/SubTickets#CreatingSubtickets means to create them].  Plan for but do not yet implement ''starts with'' and ''ends with'' dependencies.
- 1. Specify the interfaces necessary for a scheduling plugin to use dependencies, estimates, and time worked to determine project schedule.
-   * Consider adding a percentage available when scheduling resources.
- 1. Specify the interfaces necessary for a Gantt chart to get data from tickets.
-   * Each task must have a name, duration, percent complete, and start or end. (The start or end comes from schedule calculations, not direct ticket data.)
-   * Access to dependencies between tickets is also needed so as to render the chart.
- 1. Implement those interfaces on top of TimingAndEstimationPlugin.
+ * [#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.
+
+ * 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.)
+
+ * Additional dependency types can be added, perhaps by enhancing or forking !MasterTickets.
+
+ * Additional Gantt display options (e.g. critical path) can be added independent of additional dependency types.
+
+ * The scheduler can be enhanced to take into account resource conflicts.
+
+ * A calendar can provide the scheduler resource availability without affecting the Gannt chart.
+
+= Design =
 
 = Disclaimer =