This document discusses the importance of accounting for uncertainty in agile projects. It provides examples of sources of uncertainty like changing requirements, over or under estimation of tasks, and lack of technical knowledge. It recommends involving customers throughout the project, estimating uncertainty without being precise, and allocating time and resources to address defects and non-iteration work as a way to mitigate uncertainty. Estimating uncertainty helps deliver promised functionality on time and builds customer trust.

1. Uncertainty in Agile Projects A lightning talk about uncertainty