Changes between Version 2 and Version 3 of ProjectManagementIdeas


Ignore:
Timestamp:
Apr 16, 2009 8:45:15 PM (5 years ago)
Author:
ChrisNelson
Comment:

Change some headlines.

Legend:

Unmodified
Added
Removed
Modified
  • ProjectManagementIdeas

    v2 v3  
    99Trac has three Gantt chart plugins:  
    1010 
    11  * [wiki:FlashGanttPlugin FlashGantt]  
    12  * [wiki:GanttChartPlugin GanttChart] 
    13  * [http://willbarton.com/code/tracgantt/ TracGantt]. 
     11 [wiki:FlashGanttPlugin FlashGantt]:: seems complex and stale. 
    1412 
    15 !FlashGantt seems complex and stale. 
     13 [wiki:GanttChartPlugin GanttChart]:: is a very simple Gantt chart implemented in a formatted text region.  It is manually edited, not data-driven. 
    1614 
    17 !GanttChart is a very simple Gantt chart implemented in a formatted text region.  It is manually edited, not data-driven. 
    18  
    19 !TracGantt has potential but has some funky fields (e.g., Due to Assign) that don't seem to be appropriate to what we want to do with a Gantt chart. 
     15 [http://willbarton.com/code/tracgantt/ TracGantt]:: has potential but has some funky fields (e.g., Due to Assign) that don't seem to be appropriate to what we want to do with a Gantt chart. 
    2016 
    2117There is a [http://www.viewpath.net/Website/ganttcharts/googlegadget.aspx Google Gadget Gantt chart] which might be leveraged for the visualizations once the data is made available. 
     
    3935== Component Data == 
    4036 
    41 Each Gantt chart component or feature requires data to support it.  For Trac-based project management, this data is often in addition to the core ticket data.  Core ticket fields include: 
     37Each Gantt chart component or feature requires data to support it.  For Trac-based project management, this data is often in addition to the core ticket data.   
     38 
     39=== Core Fields === 
     40 
     41Core ticket fields include: 
    4242 
    4343 * type (bug, task, enhancement, etc.) 
     
    5656 * description 
    5757 
     58=== Additional Data === 
     59 
    5860For a simple Gantt chart, we may use the following ticket fields: 
    5961 
     
    6870 * dependencies 
    6971 
     72It may also prove useful to note that a resource may not be applied 100% to a task. 
     73 
     74=== Timing === 
     75 
    7076While Gantt charts typically show percent complete, this can be computed from hours remaining vs. total estimate or hours worked vs. total estimate.  We will not, necessarily, store percent complete.  It is intuitive for display and analysis but difficult for data entry. 
    7177 
    72 == Dependencies == 
     78 
     79=== Dependencies === 
    7380 
    7481There are four general types of dependencies for tasks: 
     
    93100  dependencies (mastertickets does this fine) 
    94101 
    95   estimates (timingandestimation is mostly ok, but needs computation 
    96   logic a little more towards earned value) 
    97  
    98102  recording of available resources (people in hours/week) 
    99103 
     
    103107  a way to show the schedule 
    104108 
    105  
    106  
     109= Features = 
    107110 
    108111A Gantt plugin for Trac should analyze ticket dependencies and produce an interactive, explorable Gantt chart showing task progress and project status. 
     
    110113By "project", I mean a set of related milestones.  Perhaps a software project has a Design Phase, an Alpha Release, a Beta Release, and a General Release.  Each would be a milestone with a target date and tickets to complete the work for that milestone.  There must be a way to specify which milestones to include either listing explicitly or by giving a pattern or substring filter. 
    111114 
    112 The chart should be able to show all tickets, though that may be a very complex chart. 
    113  
    114 > or alternately all those tickets matched by a (query | report) or any 
    115 > other ticket group provider ;) 
    116  
     115The chart should be able to show all tickets (though that may be a very complex chart) or alternately all those tickets matched by a (query | report) or any other ticket group provider.  A "chart these" button on a report page would be very nice. 
    117116 
    118117The chart should support interactively "folding" groups of tasks to hide detail. 
    119118 
    120 Tasks/tickets in the chart should be links to the tickets they represent. 
     119Tasks in the chart should be links to the tickets they represent. 
    121120 
    122121To effectively display project progress, tickets must have estimated and actual times as in the TimingAndEstimation plugin.  Each task's bar in the chart should show actual hours. 
    123122 
    124123The chart should have a Today line 
    125  
    126 Ticket dependencies that must be supported include: 
    127  
    128   1. Task B must follow task A. 
    129   2. Task A is composed of tasks B and C.  A's estimated time is the total of B's and C's.  (SubTickets) 
    130   3. Tasks A and B start at the same time 
    131   4. Tasks A and B must end at the same time 
    132  
    133 Type 1 dependency is implemented in the MasterTicket plugin.  Note that a task may have many predecessors and many successors. 
    134  
    135 Type 2 dependency is necessary to support "folding" or "zooming" detail in the chart.  It is also generally useful and might be implemented as its own plugin that the Gantt chart could require.  Note that is should be possible to create a tree where A is composed of B and C, and B is composed of D and E, and C is composed of F, G, and H.   
    136  
    137 Types 3 and 4 are more unusual and a useful Gantt chart can be created without immediate support for these links in the first release. 
    138124 
    139125It is also desirable to have loop detection to error-proof the tool used to create dependencies.