Template for Time Estimate and Risk Analysis
Software Methodology

Table of Contents

Non-Software Deliverable Time Estimate

Deliverable Est. # of pages Est. time/page Low Expected High Person(s) Responsible
User manual typically 8-15
Design document typically 10-20
Acceptance test plan typically 10-15

Software Time Estimate

Requirement # Low Expected High Person(s) Responsible
Subtotal

For meaningful groupings of functionality
TOTAL

For the entire project

Risk Analysis

Provide a prioritized list of project risks, with each risk in a separate section.

Risk #1

Description: Description of the risk.
Probability: The probability of the risk occurring (low, medium, high)
Impact: What is the severity of the risk should it occur
Risk management: What steps are you taking to address this risk?

Last updated: 10/9/2002