Which of the following should not be included in a team’s velocity calculation?

In the context of calculating a team's velocity, it is essential to only consider work that meets the criteria for completion set by the team. Velocity is a measure of how much work a team can complete in a given timeframe, typically measured in story points or effort estimation units.

Work described as "unfinished according to the definition of done" should not be included in the velocity calculation because it does not reflect the actual output of the team. For a piece of work to contribute to velocity, it must be fully completed, which means it must adhere to the agreed-upon definition of done. This ensures that only high-quality, fully finished tasks are counted in the team's performance metrics, allowing for more accurate forecasting and planning in future sprints.

Including unfinished work would distort the velocity measurement, making it unreliable and potentially leading to poor project management decisions, as it would give a misleading impression of the team's capacity and efficiency. Thus, excluding unfinished work aligns with best practices in Scrum, focusing on delivering completed increments of work to stakeholders.