Agile Training Camp e-Learning Module Introduction -

What is velocity? None of the above The amount of work completed in an iteration, measured in ideal hours The sum of the estimates for all user stories that have been at least started in an iteration The sum of the estimates for all completed user stories minus the incomplete user stories The sum of the estimates for all user stories completed within a single iteration Introduction -Explanation -

How is velocity used? To determine which people on a team are making the most contribution To compare one team with another To maximize the work a team can perform To measure the progress a team is making during an iteration To determine the amount of work that can fit within an iteration Introduction -Explanation -

Should velocity be used to compare teams? Velocity is calculated from User Story estimates that are only qualitative – the User Stories are sized relative to each other, but not against any fixed scale. Introduction -Explanation -

Why should a team not try to maximize its velocity? Agile projects are structured so that teams can enter a cadence or rhythm that is indefinitely sustainable. Velocity gives teams an idea of how much work the team can reasonably fit within an iteration. Attempts to fit more work into the iteration (thus increasing the team’s velocity) will only cause stress resulting in a pace that is not sustainable. Introduction -Explanation -