Agile life cycles (see Figure 65, Gantt-like picture of an agile life cycle) handle schedule, technical, requirements, and cost risks the best. They plan to complete features—most often the most valuable features—within a short timeboxed iteration. These life cycles require frequent access to the customer or customer surrogate. (In one-week iterations, the customer needs to be available for questions every day.) As long as the team members are not multitasked onto several projects, leave in the middle of a timebox, and can commit to completing features, the team is likely to succeed with this life cycle.