1 to 13 of 13
Today we received this feature request:
Is there any report which provides an 'estimates vs actuals' where we can track actual head hours against the estimated hours for each task in a project? We are already entering the 'estimated hours' for a task and developers are clocking up time against the tasks so it would seem the data is there to do this. Ideas?
This would be so useful. It would allow us to quickly pinpoint where exactly the budget is going. The worktypes and modules are to general. As a workaround we define worktypes to be able to track with more detail. This makes setting up a new project quite timeconsuming.This would add a lot more value for us!
We are going to retrofit the Project Activity Report by Task to include the task level estimated hours. This one report will allow you to see each task estimate and the exact hours that have gone into each task.We are also kicking around the idea of adding an additional view to the Estimated vs. Actual page at the project level. It currently shows the estimated hours that have been entered for the project against all of the actual hours that have been logged. This new view would be similar, but would show the estimated hours summarized from all of the tasks that have been created for the project. For example:Estimated Hours from tasks: 80Budgeted estimated: 110Difference: 30Good idea? Would you use it?
## Update ## Last night we launched a new batch of updates including an update to the Project Activity Report. Now the Project Activity Report displays the estimated hours for each task (note: only if the "by Task" filter is selected when running the report). The top half of the report includes the summarized hours and the bottom half includes each time entry for each task and the estimate:
Hi. I'm in my trial period for Intervals. Here's the deal-maker for me: My end is to be able to let staff know how they are doing on estimate vs actuals for a month, a quarter or a year. In the time management software I'm using now, I can pull a report that has that info, but with a problem: that I'm hoping you've solved: Say a project has 40 hours. If I'm looking for a report for December, and the project has 20 hours spent in December, and 20 in January, the current software shows that we've done 20 out of the 40 hours, and therefore looks like we're well under budget. This is a huge problem because no matter what time span I select, the report always contains partial projects. Is there a way to show this information per employee? I think Michael's comment on May 14th 2008 would may do the trick - being able to see an aggregate view of all projects.Thanks,David
Michael,This is a terrific product, but I'm still having trouble understanding the use of project-level and task-level work estimates that are not connected.In your example above there is a project budget estimate of 110 hours and a task estimate of 80 hours. The first question that pops into my head is -- how else would somebody estimate the total project hours except by summing the estimated work by tasks?? I guess a client with a specific budget could give you a figure to work backward from, but you would still have to align the task estimates with that figure. Either way, the task-level and project-level estimates should match.The most irksome aspect of having the disconnected work estimates is that I have to enter the figures twice...once at the task level, and then again at the project level. Please reconsider the current set up and link the two figures together.
I just have to throw my vote in here too. By my thinking, and in our processes, total time estmiated for any project is the sum of time estimates for all tasks in the project. The seemingly strange disconnect between estimated task time and estimated project time might prevent our adoption of Intervals.I hope that you will soon reconcile those two perspectives of time estimates. Otherwise, Intervals seems like a winner.Thanks!Mike
It might be useful to give some additional back story on the intent of estimates within Intervals since there are project estimates and task estimates. The most common way is to use the project estimates to set the high level budget for the project and then use the task estimates as a control/reality check for the project. It is a top down vs. bottom up view. On the Pelago web development side of our business we sell contacts that have the total number of hours included for the project then use the task estimates as an early indicator if the project is going to go over what was contracted. We typically do not update the project estimates after the project starts. If you are interested in seeing hours only based on task estimates there are a variety of ways to get at that data.
Comments are closed.For more Intervals help documentation, please visit help.myintervals.com