Effort Estimation Template
- Thread starter Jupiter
- Start date
TomBascom
Curmudgeon
There isn't really such a thing as "Progress development". You are almost certainly developing within an application framework of some sort. Either that dictated by a partner application or one has been adopted by your company.
Even if it is a partner framework there are likely significant local variations in practice.
In the past I have found it helpful to try to create such templates by creating broad groups of common tasks that are relevant to the work being done. Things like reports, screens, calculations etc. Each of those tends to have "drivers" that can be used as estimators (things like the number of fields on a screen or the number of joins in a report) along with various "overhead" (maybe it usually takes 2 hours to format the headers for a report). You can then calibrate your estimates based on local experience and practices. (This is in many ways a "function point" oriented way of estimating.)
Even if it is a partner framework there are likely significant local variations in practice.
In the past I have found it helpful to try to create such templates by creating broad groups of common tasks that are relevant to the work being done. Things like reports, screens, calculations etc. Each of those tends to have "drivers" that can be used as estimators (things like the number of fields on a screen or the number of joins in a report) along with various "overhead" (maybe it usually takes 2 hours to format the headers for a report). You can then calibrate your estimates based on local experience and practices. (This is in many ways a "function point" oriented way of estimating.)
Similar threads
- Locked
- Jessica Kent
- Progress Blog
- Locked
- Scott Snowden
- Progress Blog