Scrum Performance Metrics

Correct Answer: Scope reduction

A sharp decline in the remaining effort near the end of the sprint typically indicates a scope reduction. This is because a significant amount of work is suddenly removed or deemed no longer necessary, which leads to a rapid decrease in the amount of effort required to complete the sprint. The other options are less likely: 'Increased team productivity' might lead to a steady decline in remaining effort but would not typically result in a sharp drop near the end. 'Tasks were underestimated' would generally be discovered earlier in the sprint as tasks are being worked on, not abruptly at the end. 'Technical difficulties resolved' could potentially lead to a decrease in remaining effort, but it would not usually cause a sharp decline unless a significant bottleneck affecting many tasks was resolved all at once, which is less common.

Correct Answer: Investigate the reason for the sudden increase and whether it's sustainable.

The sudden increase in velocity may not necessarily mean a sustained or permanent increase in team productivity. As a Scrum Master, understanding the reason behind the sudden spike is essential before taking any further action. If the team has been able to increase velocity because of some specific changes or practices, it may be worth considering scaling them. On the other hand, if the spike is because of extra hours of work or other unsustainable practice, it may lead to potential burnout. The other answers suggesting celebrating the success, increasing the sprint commitment, or assuming increased efficiency without delving into the reason behind the spike may potentially lead to unviable expectations and practices.

Correct Answer: A tool used to track the amount of work the team completes in each sprint over time.

In Scrum, a velocity chart is a tool used to track the amount of work the team completes in each sprint over time. It isn't designed to predict future performance based solely on past performance, so the second answer is incorrect. It also doesn't dictate how quickly the team needs to work, making the third answer incorrect. Lastly, it's intended to track team performance as a whole, not individual output, so the fourth answer is also incorrect.