If the amount of new functionality to be developed is fixed, how should a good release plan account for the project uncertainties?
- By providing a date range for project completion.
- By keeping the project open-ended.
- By providing an estimate of standard deviation along with the deadline estimate.
- By keeping the completion estimates within the team.
If the amount of new functionality is fixed, state your uncertainty as a date range rather than providing a single completion date estimate. The rest of the choices are not recommended Agile practices. [Cohn, M., 2006. Agile Estimating and Planning. 1st ed. Massachusetts: Pearson Education. Page 248]