Do you use "Stories Overview" report to find out where the project is at?
A common question for every project manager is "where is my project at"? This question isn't just asked to find out how many tasks are done, but also to understand if all these tasks are done to meet users' requirements.
Both the Visual Studio Scrum and MSF for Agile project templates in TFS 2010 and 2012 provide a built-in "Stories Overview" report to help you find out where the project is at, as well as to tell you if all the tasks are well tested.
Figure: The developer says he is 90% done... the report shows 25% tested, but 0% passed! Tip: Set this up on a daily schedule so the Scrum Team get this in their inbox each day.
Suggestion for Microsoft #1: Add a Summary Number in large font at the top, eg. 55% complete.
Suggestion for Microsoft #2: Add this great report to the Microsoft Scrum TFS Process Template.
Where are we at?
TFS’s Stories Overview Report is the best tool to solve the common question project managers ask the developers “Where are we at?”
The problem with the answer is that developers almost always say 90%
Need to know $$$, read Do you get regular updates on costs and progress (aka Project Progress, Burndown, Story Overview)? to see which reports you need to get a complete project progress overview.