Forum Discussion
How to Find Remaining Work from Azure DevOps Data
In Azure DevOps, you should be able to retrieve the iteration start and end date. From this you can define what the current iteration is as the current iteration is essentially the iteration where the current date is between the iteration start date and iteration end date.
The total work outstanding for the current sprint would be all the items in the current iteration that are not completed.
I these articles:
- https://www.linkedin.com/pulse/sprint-burndown-charts-powerbi-ferry-van-der-vorst/?trackingId=o5Ze1Az4TpGWjZJnqIAknA%3D%3D
- https://www.linkedin.com/pulse/sprint-burndown-charts-powerbi-part-2-ferry-van-der-vorst/?trackingId=o5Ze1Az4TpGWjZJnqIAknA%3D%3D
I described how to create a velocity chart, which shows you the work completed per day in an iteration.
Hope this helps.
In Azure DevOps, you should be able to retrieve the iteration start and end date. From this you can define what the current iteration is as the current iteration is essentially the iteration where the current date is between the iteration start date and iteration end date.
The total work outstanding for the current sprint would be all the items in the current iteration that are not completed.
I these articles:
- https://www.linkedin.com/pulse/sprint-burndown-charts-powerbi-ferry-van-der-vorst/?trackingId=o5Ze1Az4TpGWjZJnqIAknA%3D%3D
- https://www.linkedin.com/pulse/sprint-burndown-charts-powerbi-part-2-ferry-van-der-vorst/?trackingId=o5Ze1Az4TpGWjZJnqIAknA%3D%3D
I described how to create a velocity chart, which shows you the work completed per day in an iteration.
Hope this helps.