Changes between Version 15 and Version 16 of ProjectManagementIdeas


Ignore:
Timestamp:
Apr 28, 2009 10:27:12 PM (5 years ago)
Author:
ChrisNelson
Comment:

More edits. Not done yet.

Legend:

Unmodified
Added
Removed
Modified
  • ProjectManagementIdeas

    v15 v16  
    104104 * percent effort 
    105105 
    106  
    107 === Timing === 
    108  
    109 While 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. 
    110  
    111 = Features = 
     106'''NOTE:''' While Gantt charts typically show percent complete, this can be computed from time remaining vs. total estimate or time worked vs. total estimate.  We will not, necessarily, store percent complete.  It is intuitive for display and analysis but difficult for data entry. 
     107 
     108= Related Work = 
     109 
     110MasterTicketsPlugin supports FS dependency (but calls it ''blocks'' and ''blocked by''). 
     111 
     112The [http://trac.edgewall.org/wiki/SubTickets SubTickets] page talks about adding composition type dependency.  Can this be done in a plugin like !MasterTickets or must it be in the core? 
     113 
     114TimingAndEstimationPlugin and TracHoursPlugin add estimated and actual hours fields to tickets.  There is some disagreement about whether the estimate is the remaining time (so total estimated time is actual + estimate) or total time (so remaining time is estimate - actual).  A Gantt chart typically wants estimate and percent complete.  It is possible to extract this from either recording convention and we should likely allow either convention via a configurable interface. 
     115 
     116There 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 (e.g. using [http:https://opensvn.csie.org/traccgi/swlcu/wiki/En/Devel/TracGViz/ TracGViz plugin}}}). That widget is developed and maintained by a company (i.e. [http://www.viewpath.net/ ViewPath]). Besides users need access to the internet and their projects environments '''have to''' be available too so that the iGoogle container be able to retrieve the data to display in the chart. All this means that local deployments (intranets, ...) are not possible. 
     117 
     118= Design = 
    112119 
    113120A Gantt plugin for Trac should analyze ticket dependencies and produce an interactive, explorable Gantt chart showing task progress and project status. 
    114121 
    115 By "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. 
     122By "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 phase would have a milestone with a target date and tickets to complete the work for that phase.  There must be a way to specify which milestones to include either listing explicitly or by giving a pattern or substring filter. 
    116123 
    117124== What do we need in the back end ? == 
     
    129136A "chart these" button on a report page would be very nice. 
    130137 
    131 Tasks in the chart should be links to the tickets they represent (preferently opened in a separate tab | window). 
    132  
    133 Milestones should be displayed in the chart as well 
     138Tasks in the chart should be links to the tickets they represent (preferentially opened in a separate tab or window). 
     139 
     140Milestones should be displayed in the chart as well. 
    134141 
    135142The chart should support interactively "folding" groups of tasks to hide detail. 
    136143 
    137 Zooming in order to see the WBS in more detail 
    138  
    139 Panning or scrolling in order to display the schedule at a  
    140 different time. 
     144Zooming in order to see the WBS in more detail. 
     145 
     146Panning or scrolling in order to display the schedule at a different time. 
    141147 
    142148Each task's bar in the chart should show actual hours. 
    143149 
    144 The chart should have a Today line 
     150The chart should have a Today line. 
    145151 
    146152The chart (or an accompanying report or tool) should aid in resource leveling by (at least) showing overcommitted resources.  
    147153 
    148 Visual indications about delays, task completion and other  
    149 significant events 
    150  
    151 Drag n' Drop so that users can change the order of the tickets (yes, I'm drunk ... hip .o: ) 
    152  
    153 = Related Work = 
    154  
    155 MasterTicketsPlugin supports FS dependency (but calls it ''blocks'' and ''blocked by''). 
    156  
    157 The [http://trac.edgewall.org/wiki/SubTickets SubTickets] page talks about adding composition type dependency.  Can this be done in a plugin like !MasterTickets or must it be in the core? 
    158  
    159 TimingAndEstimationPlugin and TracHoursPlugin add estimated and actual hours fields to tickets.  There is some disagreement about whether the estimate is the remaining time (so total estimated time is actual + estimate) or total time (so remaining time is estimate - actual).  A Gantt chart typically wants estimate and percent complete.  It is possible to extract this from either recording convention and we should likely allow either convention via a configurable interface. 
    160  
    161 There 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 (e.g. using [http:https://opensvn.csie.org/traccgi/swlcu/wiki/En/Devel/TracGViz/ TracGViz plugin}}}). That widget is developed and maintained by a company (i.e. [http://www.viewpath.net/ ViewPath]). Besides users need access to the internet and their projects environments '''have to''' be available too so that the iGoogle container be able to retrieve the data to display in the chart. All this means that local deployments (intranets, ...) are not possible. 
     154Visual indications about delays, task completion and other significant events. 
     155 
     156It would be nice to be able to create task dependencies graphically using the Gantt chart as a GUI or to change a milestone date by dragging it along the chart. 
    162157 
    163158= Design guidelines = 
     
    196191=== Implications === 
    197192 
    198 The aforementionned separation ''should'' allow the replacement of any of the components involved. Hence the following modifications ''should'' be made easily (the list being intentionally incomplete) : 
     193The aforementioned separation ''should'' allow the replacement of any of the components involved. Hence the following modifications ''should'' be made easily (the list being intentionally incomplete) : 
    199194 
    200195  - Replace the JS-based view by another made with Flash.