This document discusses how to manage iterations on agile software development teams. It describes typical meetings like the release and iteration planning meeting and standup meeting. It also discusses measuring team performance, having automated builds, using story and release walls to track progress, and holding retrospectives. The typical project structure involves a 1 year project broken into 3 month releases with 2 week iterations.