Viable Software Estimation Modeling: A Key Component Of Software Risk Management
I spoke with someone recently who explained the reason they use SEER is for risk management. They pointed out that not only can they determine the risks of schedule, effort and reliability, but the whole of SEER allows them to do risk reduction. A process improvement: no problem, a quick trade off is performed by setting the appropriate SEER parameters for process improvement, process experience, development tools and practices and they can see exactly what to expect, both good and bad. Then when asked to justify the result he can state explicitly: this includes reduction of team experience with processes, the process improvement going on during this project, any tools being deployed in the process improvement effort and the anticipated cost / benefit.
And for projects that are not challenged with new and different challenges, knowledge bases do the job without needing to concentrate on parameters.
Thank you for reading “Dan on Estimating”, if you would like more information about Galorath’s estimation models, please visit our contact page or call us at +1 310 414-3222.
Related posts:
- Software Sizing, Estimation, Risk Management Book Available in Japanese
- Step Six: Quantify Risks and Risk Analysis
- Risk / Uncertainty In SEER and Project Management
- Ten-step Project Estimation Process
- 10 Step Estimation Process Sample Checklist
Comments
Leave a Reply


