...
We see that at the Sprint Planning meeting team committed to delivering 32 story points (SPs). This metric reflects the total scope added to the sprint before hitting the “Start Sprint” button on the Jira Scrum board.
Final commitment
The "Final commitment" metric reflects any changes to an active sprint's scope - it means that if any work was added , or removed, or an issue's estimate was changed after the sprint’s start event, then these changes would be reflected in the Final commitment.
The final commitment is 36 SPs which is more than a team committed to at Sprint Planning (32 SPs). The chart (Estimation change metric) shows that this happened because the work estimate has increased.
By checking details about sprint issues (click anywhere on the area of Sprint 1), we find out that user stories' #4 and #6 estimate has been increased by 2 SPs each:
...
No work items were removed during the sprint.
Estimation change
Estimation The estimation change is 4 SPs as the estimate has increased during the sprint by 2 SPs for user stories #4 and #6.
...
User story #6 (estimated at 5 SPs) haven’t hasn’t been completed during the sprint - that’s what this metric reflects.
...
“Initial commitment” and “Final commitment” metrics are equal, with 31 SPs. However, we see that 5 SPs of work have been added, and 5 SPs have been removed. That shows that team Alpha is well acquintanted acquainted with the velocity concept, and when the scope of the sprint increases by 5 SPs, then some work should be removed from the sprint to meet the commitment.
...