Final answer:
The term for how many functions/features/user stories an Agile team completes in an average sprint is 'velocity.' It is calculated by averaging the points of completed user stories over several sprints, providing a basis for future sprint planning.
Step-by-step explanation:
Agile Team's Work Measurement
The term that describes how many functions, features, or user stories an Agile team completes in the average sprint is known as the team's velocity. Velocity is a measure used in Agile project management that represents the average amount of work a team can complete during a sprint. It is calculated by adding up the points for all fully completed user stories at the end of the sprint and averaging this amount over several sprints to gain a consistent measurement. This metric helps the team estimate how much work they can handle in future sprints and is a vital component of sprint planning.
For example, if an Agile team completes 50 points worth of user stories in Sprint 1, 40 in Sprint 2, and 60 in Sprint 3, the average velocity would be calculated as (50 + 40 + 60)/3, which equals approximately 50 points per sprint. Consequently, the team would use this average to forecast the work they can commit to in upcoming sprints.
Understanding velocity aids Agile teams in becoming more predictable and efficient in their sprint planning. It allows them to set realistic sprint goals based on their past performance. However, it is important for Agile teams to focus on sustainable work habits rather than inflating their velocity unrealistically.