Why Team Velocity Report and Query does not match?
We need information on how Team Velocity report is calculated. We committed user stories on first day of iteration, then several user stories were removed later in the iteration. When we ran a query to see user story point delivered per iteration; the result is different than Team Velocity report. The query provides accurate information.
I read a question from another person the "scenario" seems to be the same, how ever in her case the solution was related to fixing an user introduced error on the Project Configuration Source, the complexity enumeration for an OOTB Scrum project... I tried to check the values using the web client and it looks like we have the OOB values... Any ideas?
Thank You |
Be the first one to answer this question!
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
First question: Is your data warehouse getting updated reliably? Most reports are based off of the data in the warehouse, not "live" data that queries work with. Technically, the data sources are different (though should be in synch if things are running as expected). Since DW/ETL jobs run once a day in most environments, some changes won't be visible in the reports until the next day.