I wrote earlier about the importance of Software estimation procedure. I would like to highlight the latest research on software estimation and share few tips in this post.
"
"What We Do and Don't Know about Software Development Effort Estimation" in IEEE Software, March-April 2014 issue, where he reviewed the software effort estimation and suggested the following guidelines
Which one is larger? Relative estimation can introduce biases |
"
- Develop and use simple estimation models tailored to local contexts in combination with expert estimation.
- Use historical estimation error to set minimum-maximum effort intervals.
- Avoid exposure to misleading and irrelevant estimation information.
- Use checklists tailored to own organization.
- Use structured, group-based estimation processes where independence of estimates are assured.
- Avoid early estimates based on highly incomplete information."
"
- Make Comparisons to Similar Projects and Use Work Hours
- Attend to Unique Properties of the Reference Project
- Attend to Estimation Sequences
- Avoid Using Small User Stories as References
- Attend to Request Formats
- Use Combinations of Independent Estimates"
Going through the above checklists can help you identify areas of improvement. Make a beginning by reviewing your recent experience of project estimation against the above guidelines and share your experiences/challenges.