Software Project CR Effort Estimation guideline

Change Management Estimating Information Technology

Punchihewage Don Rishan Ranganath Yasarathna Kadawatha, Sri Lanka

Is there any established evaluation criteria for estimating Change Request (CR) efforts in software development projects currently in the maintenance phase?

According to the client’s guidelines, effort estimates should be proportionate to the total development efforts as follows:

QA Effort: 20% to 30% of Development Effort
BA Effort: 10% to 15% of Development Effort
PM Effort: 10% to 15% of Development Effort
UAT Effort: 5% to 10% of Development Effort

In the context of CR development within a maintenance project, achieving these ratios, particularly for QA efforts, is challenging. Is there any project management guidance or reference that could support deviations from these ranges?

Posted: Nov 14, 2024 3:47 AM

Kiron Bondale Retired | Mentor| Retired Welland, Ontario, Canada

No, as this is context dependent so any such benchmarks would either be inapplicable general averages or would have to come from a very specific set of highly similar projects. A simple example of this is comparing the testing effort involved between one application which has comprehensive automated regression testing and one where no such automation exists.

Kiron

Posted: Nov 14, 2024 4:22 AM

Please login or join to reply

Software Project CR Effort Estimation guideline

Sponsors

Vendor Events

Guessing is not a strategy: How to build decision velocity with AI and real-time data

Newsletters