Changes between Version 107 and Version 108 of ProjectManagementIdeas


Ignore:
Timestamp:
Aug 1, 2011, 5:20:02 PM (13 years ago)
Author:
Chris Nelson
Comment:

Clean up some more old notes

Legend:

Unmodified
Added
Removed
Modified

  • ProjectManagementIdeas

    v107 v108  
    22
    33Trac 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.
     4
     5In Trac, "project" is sometimes used synonymously with "installation."  As used on this page, it is a set of related tasks and deadlines.  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. 
    46
    57= Related research =
    … …  
    460462 risk:: Relative risk.  An integer from 0 to 100.  How likely it is that ''work'' is accurate.  Zero means no risk; ''work'' is certain to be accurate.
    461463 priority:: Relative priority.  An integer.
    462  percentComplete:: How much of ''work'' is done?
     464 percentComplete:: How much of ''work'' is done? (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.)
    463465 resource:: Name of resource assigned to this task
    464466 percentEffort:: How much of ''resource's'' time is spent on the task.
    … …  
    586588 * percent effort
    587589
    588 '''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.
    589 
    590590
    591591A Gantt plugin for Trac should analyze ticket dependencies and produce an interactive, explorable Gantt chart showing task progress and project status.
    592592
    593 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 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.
    594 
    595 == What do we need in the back end ? ==
    596 
    597 The 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. 
    598 
    599 It would be nice to be able to choose an As Late As Possible or As Soon As Possible algorithm for laying out tasks.
    600 
    601593== What do we need in the user interface ? ==
    602594