[Collaboa] time estimates

[Michael Fairchild]

Sounds like Tom already ahs implemented some timetracking and 
estimating. I will have to update my version of collaboa to check it 
out.  I am running on the last release.

Esad Hajdarevic wrote:
> Hello!
>
> Well, as the changes of /Total time/ are saved, one can always extract 
> all the changes from the /Current total time/ to get the /Original 
> estimate/ and see the difference between these.
Not quite sure about that would be able to provide what i have in mind.  
What i mean by original estimate is to have a column 
original_estiamted_hours to be stored at ticket creation time, or when 
ticket is marked in progress or approved or whatever is the trigger to 
say, "this ticket has now been estimated.  It is not just a request."  
You might even want to record a column of originally_estimated_by ( i 
actually think this would be wayy down the road, and maybe never as it 
might be bloat.) 
  Of course, hopefully the estimated_hours is updated along the way so 
that it is more than the actual hours before the actual hours grow to 
close or beyond the previous estimate.  That is why you would need a 
special field for originaly_estimated_hoursl; or you could just use the 
acts_as_versioned mixin.
> I think that in order to integrate billing, one should first solve the 
> assignement of tickets (See http://dev.collaboa.org/tickets/12) (this 
> would be your bill_to column).
I actually see the assigned to task to be used as a reference to which 
employee would be doing the work.  This would either tie into a new 
"employees" table, or the users table.  The bill_to would be a 
customer_id refrenceing the customer to bill.  I am not suggesting 
collaboa should necessarily have all this functionality, just how i am 
trying to implement it in my app and how would do it in collaboa if it 
were to be done.
>
> @Accuracy of estimating: It would be nice to have (at some point in 
> future) some kind of Statics module where different stats can be seen: 
> average accuracy of estimation, checkins/day, lines of code/day etc.
>
> Greetings,
>
> Esad
>
> Michael Fairchild wrote:
>
>> I think this sounds great.  I am writing a timecard/estimating app 
>> for a boatyard now and i just have a table of timecards and a table 
>> of estiamate_lines.  Timecards and estimate_lines both belong to each 
>> other and i can get all the data i need from this.  One thing i do 
>> not have, but like, and may implement is the original_estimated_hours 
>> idea.  Would be nice to have so you could have an indicator as to how 
>> accurate your estimating is, and hopefully improve.    Having a table 
>> of timecards it is easy to create added functionality/invoices if you 
>> want later on.  Adding billable, billed, and bill_to fields would 
>> make this pretty easy.  I would ignore billing in the beginning tho.
>>  just one way, I know there are plenty of good ways to do this.  Mine 
>> is only one that is working for me.
>> ~Michael
>
>
> _______________________________________________
> Collaboa-talk mailing list
> Collaboa-talk at lists.collaboa.org
> http://lists.collaboa.org/mailman/listinfo/collaboa-talk