ProjectTRACKER Help - Estimates

The estimation function of the ProjectTRACKER provides statistical estimation tools. The typical estimatation page looks like:

Note: Only users with “Estimate” access rights can see and use the estimation functionality!

Selection Filters

Task Task filter.
Program Program filter.
Task-ID Filter for task id.
Task-Group Filter for task group.
Task-Prio Task prio filter. Prio must be given in format: 1,2,3 …
Task Owner Task Owner filter.
Task Status Task Status filter.

Selection Options

Task Confidence The confidence interval of the Conf. Case calculation. 90% means that from a statistical point of view 90% of the “real” effort estimates should be included in the calculated Conf. Case value. The statistical calculation is based on that the Effort Measured values are equally distributed around the Effort Planned values, if this is not the case the calculations are wrong!. Higher confidence intervalls should be used to communicate save margins, e.g. to external customers. A 50% confidence intervall is given by the Expected Case formula - this is recommended for internal plannings.
Estimate Confidence The confidence level of the task estimates, e.g. a 70% confidence level means that 7 out of 10 values are in the range of Effort Worst Case to Effort Best Case. 70% is already a “optimistic” value - typically SW efforts are underestimated and tend to overshoot the worst case assumption.
excel3.jpg Export current estimate view data to MS Excel sheet.
Opens the Reports page showing all reports including 6 in the report view.

Estimates Inline Report

The estimates inline report with the name _Estimates Page Report is shown right to the Selection form when defined by a user with “Report” rights.

Tasks Estimates Grid

ID1) Internal ID of the task record. Clicking on the task ID will select only this task. A tool tip with the task description is shown when moving the mouse cursor over the ID field.
Trend of the last change to Effort Planned. Clicking on the icon will open the Task History / Trending.
Group2) Name of the task group.
Prio3) Prio of this task - in case task is done (remaining effort is 0) the task prio is shown in green.
Task Name4) Program : Task Name.
Start Date5) Task Start Date.
End Date6) Task End Date.
Task Owner7) Task owner - if defined, users with “Own Task” right can change the task content, even when not the record owner or in the group of the record owner.
Task Status8) Task status9). Note: For Summary Tasks the task status shows the lowest status of all tasks belonging to the summary group.
Effort Best Case10) Best case effort estimation see “Software Estimation”11) page 106ff. These values have to correlate to the Estimate Confidence, means all effort estimations should be in the defined confidence range.
Effort Planned12) Most likely effort estimation see “Software Estimation”13) page 108ff. The statistical model is based on that the “real” Effort Measured values are equally distributed around the Effort Planned values, if this is not the case the calculations cannot be trusted!.
Effort Worst Case14) Worst case effort estimation see “Software Estimation”15) page 106ff. These values have to correlate to the Estimate Confidence, means all effort estimations should be in the defined confidence range.
Expec. Case Expected Case := (Effort Best Case + 4.0 * Effort Planned + Effort Worst Case) / 6.0 see “Software Estimation”16) page 109.
Stand. Dev. Standard Deviation := SQRT( SUM17)( SQUARE( ( Effort Worst Case - Effort Best Case) / DIVISOR(Estimate Confidence) ) ) ) see “Software Estimation”18) page 124.
Conf. Case Confident Case := Expected Case + FACTOR(Task Confidence) * Standard Deviation see “Software Estimation”19) page 121.
Effort Exp. Case20) Expected effort - should be based on Conf. Case estimates. Clicking on □ Copy will copy all Conf. Case over to Effort Exp. Case, clicking on the Conf. Case link will only copy over this value. Calculated values are shown in grey - when you want to save the calculated values press the Update button!
Effort Alloc. Shows the allocated Plan effort. Clicking on the link will call directly the Plan page for this task. Moving the mouse cursor over this field will show the resource allocation in a tool tip.
Effort Meas. Effort Measured := Effort Done + Effort Remaining from Efforts.
MRE Magnitude of Relative Error (MRE) := 100 * (Effort Planned - Effort Meas) / Effort Meas see “Software Estimation”21) page 110.
Metric O: Percentage of task values which are out of the Effort Best Case to Effort Worst Case boundary - see also Estimate Confidence.
M: Percentage of task values under or over the “likely” Effort Planned value. ~0% means the efforts are perfectly distributed around the Effort Planned values - see also description for Effort Planned.
W indicates the record is write protected. To still write to your own records choose another filter criteria to reduce the list to entries you are allowed to write.

Notes:

  • You need “Plan” access rights to use and access the Plan page!
  • In general all estimates and calculations should be cross checked for plausibility and consistency ;-).

Tasks Schedule Buttons

Update Store task entries.
Cancel Reload page without storing.

References

22)Software Estimation - Demystifying the Black Art, Steve McConnell, Microsoft Press 2006

1) , 2) , 3) , 4) , 5) , 6) , 7) , 8) , 10) , 12) , 14) , 20) Clicking on the headline will also sort the column
9) Configurable by the ProjectTRACKER PHP administrator
11) , 13) , 15) , 16) , 18) , 19) , 21) , 22) Ref Software Estimation
17) Over all individual values of a Task Summary Group
 
tracker/estimates.txt · Last modified: 2012/09/23 16:57 (external edit)
 
Except where otherwise noted, content on this wiki is licensed under the following license:(C) 2012 ProjectTRACKER - A. Welz. All rights reserved.
Recent changes RSS feed Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki