Changes between Version 23 and Version 24 of ProjectManagementIdeas

Timestamp:

Apr 29, 2009, 5:25:52 PM (15 years ago)

Author:

Chris Nelson

Comment:

Revising roadmap, with examples.

ProjectManagementIdeas

@@ -240 +240 @@
 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 Gantt ==
+
+There is some benefit to very basic Gantt that showed just tasks and their dependencies and the resultant schedule.
+
+[[Image(simple-gantt.PNG)]]
+
+Disregarding any resource constraints, this chart shows that circuit board design and firmware development follow schematic design, package design can proceed independently, assembly can't be done until the circuit boards and packaging are ready, and the product can't ship until it's assembled and has firmware.  (Clearly this is a gross simplification and likely not accurate in many ways.)
+
+This requires only that the ticket have some information about estimated effort or duration of the task and simple FS task dependency.
+
+== Plan of attach ==
+
+
  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.