Changes between Version 3 and Version 4 of ProjectManagementIdeas


Ignore:
Timestamp:
Apr 16, 2009, 9:08:15 PM (6 years ago)
Author:
ChrisNelson
Comment:

Specify some first steps. Still incomplete but a decent discussion draft.

Legend:

Unmodified
Added
Removed
Modified
  • ProjectManagementIdeas

    v3 v4  
    9595While generally useful, the ''starts with'' and ''ends with'' dependencies are somewhat more esoteric than the others and implementation may be deferred.
    9696
    97 ----
    98 Draft garbage below this line.  Still working with it...
    99 
    100   dependencies (mastertickets does this fine)
    101 
    102   recording of available resources (people in hours/week)
    103 
    104   scheduling to show given all of the above when tasks are expected to
    105   be done
    106 
    107   a way to show the schedule
    108 
    10997= Features =
    11098
     
    131119= Related Work =
    132120
    133 MasterTickets
     121MasterTicketsPlugin supports ''starts after''/''ends before'' dependency (but calls it ''blocks'' and ''blocked by'').
    134122
    135 TimeingAndEstimation
     123The [http://trac.edgewall.org/wiki/SubTickets SubTickets] page talks about adding ''composed of''/''part of''-type dependency.  Can this be done in a plugin like !MasterTickets or must it be in the core?
    136124
    137 TracHours
     125TimingAndEstimationPlugin 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.
     126
     127= Roadmap =
     128
     129There 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.
     130
     131 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.
     132 1. Specify the interfaces necessary for a scheduling plugin to use dependencies, estimates, and time worked to determine project schedule.
     133   * Consider adding a percentage available when scheduling resources.
     134 1. Specify the interfaces necessary for a Gantt chart to get data from tickets.
     135   * Each task must have a name, duration, percent complete, and start or end. (The start or end comes from schedule calculations, not direct ticket data.)
     136 1. Implement those interfaces on top of TimingAndEstimationPlugin.
    138137
    139138= Disclaimer =