Visual studio alm 2012 reporting overview
1 like618 views
The document outlines reporting options in Microsoft Visual Studio 2012 Team Foundation Server, detailing built-in reports, Excel, and SQL Server Reporting Services (SSRS). It covers various report types for tracking bugs, build activities, project health, testing activities, and agile methodologies, including Scrum and CMMI frameworks, to monitor team performance and workload. Additionally, it provides insights on creating ad-hoc reports and managing work items within different process templates.
Visual studio alm 2012 reporting overview
- 1. Microsoft Visual Studio 2012 Team Foundation Server Reporting Angela Dugan ALM Practice Manager Polaris Solutions Angela.Dugan@PolarisSolutions.com
- 2. Angela Dugan Mobile Solutions Project Leadership .NET Solutions Application Lifecycle Management
- 4. AGENDA What reporting options are available? Built-in Excel SSRS What reports come out of the box? Creating your own reports
- 5. REPORTS BY TEMPLATE Tasks SCRUM Agile CMMI Monitor bug activity, reactivations, and trends. Track bugs that the team is finding and the progress that the team is making toward fixing them. •Bug Status Report •Bug Trends Report •Reactivations Report •Bug Status Report •Bug Trends Report •Reactivations Report Monitor build activity, success, and trends. You can use build reports to track the quality and success of your team's builds over time. •Build Success Over Time Report •Build Summary Report •Build Quality Indicators Report •Build Success Over Time Report •Build Summary Report •Build Quality Indicators Report •Build Success Over Time Report •Build Summary Report Track project health, team burn rate, and task completion. Use to review the level of effort that the team has spent on each requirement type work items that the team is implementing. By using this report, you can quickly determine whether any work was recently completed on each item,what work is remaining and how far each item has been implemented and tested. You can review this report daily or weekly to monitor the progress of the team during an iteration. •Release Burndown(Scrum) •Sprint Burndown(Scrum) •Velocity (Scrum) •Burndownand Burn Rate Report (Agile) •Remaining Work Report •Status on All Iterations Report •Stories Overview Report (Agile) •Stories Progress Report (Agile) •Burndownand Burn Rate Report (CMMI) •Remaining Work Report •Status on All Iterations Report •Requirements Progress Report (CMMI) •Requirements Overview Report (CMMI) Determine added work. You can use the Unplanned Work report to determine how much work the team added to an iteration after it started. •Unplanned Work •Unplanned Work Monitor testing activity. You can use the test reports to track the team's progress toward developing test cases and to determine how well they cover the requirement type work items. •Test Case Readiness Report •Test Plan Progress Report •Test Case Readiness Report •Test Plan Progress Report •Test Case Readiness Report •Test Plan Progress Report
- 6. SCRUM -RELEASE BURNDOWN Understand how quickly your team has delivered backlog items and track how much work the team must still perform to complete a product release. Review the report to determine the progress that your team has made in a release and to answer the following questions: How much work remains in the release? How quickly is your team working through the product backlog?
- 7. SCRUM -SPRINT BURNDOWN Displays the following pieces of data: The Ideal Trend line indicates an ideal situation in which the team burns down all of the effort that remains at a constant rate by the end of the sprint. The In Progress series shows how many hours remain for tasks that are marked as In Progress in a sprint. The To Do series shows how many hours remain for tasks that are marked as To Do in a sprint. Review the report to determine the progress that your team has made in a release and answer the following questions: How much work remains in the sprint? Is your team on track to finish all work for the sprint? When will your team finish all work for the sprint? How much work for the sprint is in progress?
- 8. SCRUM -VELOCITY Based on the velocity of previous sprints that the report illustrates, you can: Track how much effort your team has reported as complete for each sprint. Estimate how much backlog effort your team can handle in future sprints if your team composition and sprint duration stay constant. Review the report to determine how much progress your team has made and to answer the following questions: How much effort has your team completed in each sprint? What is the maximum velocity of your team? What is the minimum velocity of your team? What is the average velocity of your team?
- 9. AGILE -BURNDOWN You can use this report to answer the following questions: Is the team likely to finish the iteration on time? Will the team complete the required work, based on the current burn rate? When can the team finish the current iteration? How much work can the team complete in the available time? How much work does each team member have? How fast is the team completing remaining work? Is the team adding work during the iteration? Is there scope creep? How is the work distributed across the team?
- 10. AGILE –REMAINING WORK Number of Hours vs. Number of Work Items Review the report to determine the progress within an iteration or over time. Specifically, you can find answers to these questions: How fast is the team burning down remaining work? Is work being added during the iteration? Is the team expanding the scope of the work? How much progress can the team make in the available time? Approximately when can the team finish the work? Is too much work in progress? Is the flow of work being impeded or blocked? When will the team finish the current iteration?
- 11. AGILE –ITERATIONS STATUS This report displays the following information: Stories Closed: number of user stories that have been closed; derived from the current values specified for the iteration and the state of each user story. Progress (Hours): represents the values for Original Estimate (grey), Completed (green) and Remaining (light blue) based on the rollup of hours that are defined for all tasks; derived from the current values that are specified for the iteration and the hours for each task. Bugs: representation for all bugs, grouped by their current states of Active (blue), Resolved (gold) and Closed (green); derived from the current values that are specified for the iteration and the state of each bug.
- 12. AGILE–ITERATIONS STATUS Review the report to determine how many stories are ready to release and to better understand the rate of the team's progress. For example, you can find answers to the following questions: Did the scope of work for each iteration closely match the team capacity? Does the number of stories closed in each iteration correspond to your expectations? Is the team resolving and closing more bugs with successive iterations? How many stories can the team ship today? This is BAD!!!
- 13. CMMI–BURNDOWNAND BURN RATE Burndownshows the trend of completed and remaining work over a specified time period. Burndown How fast is the team completing remaining work? Is the team adding work during the iteration? Is there scope creep? How much work can the team complete in the available time? When can the team finish the work? When can the team finish the current iteration?
- 14. CMMI–BURNDOWNAND BURN RATE Burn rate provides calculations of the completed and required rate of work based on the specified time period. Burn Rate Is the team working quickly enough to finish the remaining work on time? Work Assignment How is the work distributed across the team? Should the team balance the remaining work load?
- 15. CMMI–REMAINING WORK Number of Hours vs. Number of Work Items Questions That the Report Answers Review the report to determine the progress within an iteration or over time. Specifically, you can find answers to these questions: How fast is the team burning down remaining work? Is work being added during the iteration? Is the team expanding the scope of the work? How much progress can the team make in the available time? Approximately when can the team finish the work? Is too much work in progress? Is the flow of work being impeded or blocked? When will the team finish the current iteration?
- 16. AD-HOC REPORTS IN MICROSOFT EXCEL
- 17. AD-HOC REPORTS IN MICROSOFT EXCEL
- 18. “REQUIREMENT” PROGRESS -ALL TEMPLATES
- 19. Test % passing… Code % covered… Code % changed…
- 21. Bugs are resolved steadily… Bugs count by person…
- 22. Lines of code tested… Lines of code changed…
- 23. Task hours getting completed… Tasks are getting closed…
- 24. Test are passing… Are the builds healthy? Bugs reactivations are low…
- 25. RESOURCES Process Templates Overview: http://msdn.microsoft.com/en- us/library/vstudio/ms400752.aspx Reports and Artifacts: Scrum: http://msdn.microsoft.com/en- us/library/vstudio/ff731587.aspx#monitoring Agile: http://msdn.microsoft.com/en-us/library/vstudio/dd997580.aspx CMMI: http://msdn.microsoft.com/en-us/library/vstudio/ee332487.aspx
- 26. Process area Visual Studio Scrum 2.0 MSF for Agile v6.0 MSF for CMMI v6.0 Workflow states •New •Approved •Committed •Done •Removed •New •Active •Resolved •Closed •Removed •Proposed •Active •Resolved •Closed Product planning To customize the backlog pages, see Customize the Backlog Pages. •Bug (Scrum) •Product Backlog Item (Scrum) •Agile backlogs •User Story (Agile) •Agile backlogs •Requirement (CMMI) •Agile backlogs Task and iteration planning To customize the task board, see Customize the Task Board Page. •Task (Scrum) •Agile task board •Task (Agile) •Agile task board •Task (CMMI) •Agile task board COMPARE & CONTRAST
- 27. Process area Visual Studio Scrum 2.0 MSF for Agile v6.0 MSF for CMMI v6.0 Bug backlog management Bug (Scrum) •Bug (Agile) •Triage Workbook •Bug (CMMI) •Triage Workbook Project management Impediment (Scrum) •Issue (Agile) •Issues Workbook •Issue (CMMI) •Risk (CMMI) •Review (CMMI) •Issues Workbook Test management •Test Case •Shared Steps •Test Case •Shared Steps •Test Case •Shared Steps Code review and feedback •Code Review Request •Code Review Response •Feedback Request •Feedback Response •Code Review Request •Code Review Response •Feedback Request •Feedback Response •Code Review Request •Code Review Response •Feedback Request •Feedback Response Audit trail Not supported Minimal Supported COMPARE & CONTRAST