Changes between Version 3 and Version 4 of TimeEstimationAndQuotingSpecification


Ignore:
Timestamp:
Jun 30, 2006, 7:45:38 PM (8 years ago)
Author:
russ@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • TimeEstimationAndQuotingSpecification

    v3 v4  
    2121We wish to be able to offer bounties / quote prices on a ticket.  In addition to this [http://en.wikipedia.org/wiki/Estimation_in_software_engineering time estimation] has proven to be a difficult problem for software developers.  The most commonly expressed way of becoming good at it, is to systematically record your estimations, compare that with actual output and adjust your estimations accordingly.  Toward this end, every ticket should have an estimated time on it.  The price / bounty should be expressable in either amount per hour or total cost.
    2222
    23 === Querying New Info ===
     23=== Querying Time Information ===
     24There needs to be a way to query all of the time data that we will be adding to the database.  We want this to be limitable based on time of entry, developer, billable/not billable.  We also want the capability to compare the total amount of hours spent to total estimated.
     25
    2426=== Permissions ===
     27There should be a permission structure in place to (dis)allow viewing and editing of the various bits of data we are adding.  I would like this to mirror the trac built in permissions structure as much as possible. 
     28 1. TIME_VIEW
     29 1. TIME_EDIT
     30 1. TIME_QUERY (this could possibly be tied in with TIME_VIEW)
     31 1. ESTIMATE_VIEW
     32 1. ESTIMATE_EDIT
     33 
    2534=== Web Admin Integration ===
     35
     36=== Future Feature Possibilities (A place to hold feature creep) ===
     37It would also be nice to be able to have graphs of some of the various data bits.  This could be provided through an svg/javascript graphing package.