Velocity widget discrepancy vs Sprint

[Pawel_Wielgos]

Hello,

Planned effort for analyzed Sprint is 133.

Somehow Velocity widget is counting only 106.

The same with the Velocity widget - count of work items. 

Comparing Sprint work items with Velocity widget results I can see that some of the work items  were not taken into account but I have no idea why.

What could be the reason behind this discrepancy? 

Thank you

[#2]

@Pawel_Wielgos 

Velocity chart is basing what's included in Planned Effort based on the day the Sprint started and the Stories that were in the Sprint at that time.  It does not pay attention to stories that came in later.  This can be adjusted somewhat on the Velocity chart configure widget to tell it how many days before Start of Sprint is the work considered final.  Scroll down on the chart widget to the below and you can adjust Days past start date.  

Advanced features

Display planned work for iterations

Days past start date of iteration when planned work is final

[#3]

Hey @Pawel_Wielgos - I came across this post this afternoon and this is something that we can help with in minware.

I'm not able to include screenshots but our tool is able to track work that was added/removed from a sprint after the start so that you can understand the impact on your teams work in progress.

If this is something you are still trying to solve for we would love to help!

[#4]

@Pawel_Wielgos Exactly as @Sherry_Hooe is mentioning, you can modify the chart behaviour as explained here in docs: https://learn.microsoft.com/en-us/azure/devops/report/dashboards/team-velocity?view=azure-devops#con...