Changes between Version 65 and Version 66 of ProjectManagementIdeas

Timestamp:

May 8, 2009, 5:16:43 PM (15 years ago)

Author:

Greg Troxel

Comment:

--

ProjectManagementIdeas

@@ -1 +1 @@
 [[PageOutline]]
-
 
 Trac is strong in basic, individual and small-team task management but lacks features for heavy-duty project management ''a la'' Microsoft Project, Project Manager Workbench, etc.  This page discusses those missing features and how they can best be realized.
@@ -346 +345 @@
 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.
 
+ * Tasks will be represented as tickets.
+
+ * 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.
+
+ * !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).
+
+ * We need a new resource plugin to allow describing resources and their availability. This should support notions of normal work hours, holidays, etc.
+
  * [#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.
 
@@ -356 +363 @@
  * 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 =
 
@@ -366 +371 @@
 == IProjectTask ==
 
+gdt: why isn't this just tickets?   We need a way to indicate which resources can work on which tasks.
+
 == IProjectCalendar ==
 
@@ -371 +378 @@
 
 A slightly more sophisticated implementation would track individual resource availability so that the schedule can account for vacations and such.
+
+== IProjectResource ==
+
+Describes resource availability.  May need calendar options for individuals.
+Some may want progress rates and costs, and some may not - this is surely controversial.
 
 == IProjectSchedule ==
@@ -401 +413 @@
 
   - Olemis Lang
+  - Greg Troxel
 
 ----