1. Relating Effort Reporting to Project Estimation
John Win
04/28/10

2. Agenda Introduction of current process Problems with current process
Process improvement idea
Benefits
Q&A

3. Current Process Project estimation using COCOMO II
Weekly individual effort report
Weekly progress report submission by PM

4. Problems Inaccurate input to COCOMO II
Over optimistic mentality by programmers
Vulnerable to errors of misreporting and miscommunication in ER
No clear indication of how many hours spend on each module
Failure to understand the true cost of project

5. Proposed Idea Enhance current effort reporting system
Remove “Develop Component” activity in ER
Provide capability to add project modules/FPs to the ER system
Include the type of activity performed relating to module/FPs
Adding new code
Fix bug in existing code
Rework existing code

6. Proposed Idea

7. Proposed Idea

8. Proposed Idea

9. Benefits Leverage upon existing process
Reduce mistakes from communication
Allow for easy comparison between actual effort and estimated effort
Clearer indicators of project health
Improve student learning about effort estimation by COCOMO

10. References
Barry, E. Horowitz, R. Madachy, D. Reifer, B. K. Clark, B. Steece, W. A. Brown, S. Chulani, and C. Abts (2000, January). “Software Cost Estimation with Cocomo II” (with CD-ROM). Prentice Hall PTR.
Ali Afzal Malik, Barry Boehm. “An Empirical Analysis of Effort Distribution of Small Real-Client Projects”. April 15th, 2009.

11. Questions?