How to Estimate Validation Effort for a New System
Estimate validation effort for a new system in four steps: list deliverables, size each one, add review cycles and give a range instead of one number.
Key takeaway
To estimate validation effort, list the deliverables, assign hours to each from past projects, add review and rework cycles, and present the result as a low, base and high range.
A validation estimate is easier to defend when it is built from deliverables and past data rather than a single guess.
Step 1: List the deliverables
Write down every document and activity the project needs, such as the plan, requirements, risk assessment, test scripts, execution, and the summary report.
Step 2: Size each deliverable
Assign hours to each item using a comparable past project. If you have no history, ask the people who will do the work and record their assumptions.
Step 3: Add review and rework
Each deliverable goes through review and approval, and some come back. Add those hours explicitly instead of hiding them in a contingency.
Step 4: Give a range
Present a low, base and high figure. For example, a base estimate of 300 hours with a range of 240 to 390 hours tells the sponsor how firm the number is.
Use the estimate
The base figure becomes the hours per event you enter in the Validation ROI Calculator.
FAQ
Frequently asked questions
How do I estimate validation effort for a new system?
- List every deliverable the project needs, assign hours to each one from a comparable past project, add the hours for review and rework, and present the total as a low, base and high range.
Should a validation estimate be a single number?
- No. A range is more useful than a single number because it shows how certain the estimate is. Give a low, base and high figure and state the assumptions behind each.