Home » Microsoft » 70-498 » Which three key metrics should you measure?
Your development team uses Scrum as its process framework. You need to identify key metrics for measuring the effectiveness of any process changes.
Which three key metrics should you measure? (Each correct answer presents a complete solution. Choose three.)
A. Number of story points delivered during the sprint
B. Number of tasks added to the sprint after the sprint starts
C. Number of bugs reported by testers
D. Number of classes in the code-base
E. Number of items added to the Product Backlog
F. Number of manual test cases created
Correct Answer: ABC
Explanation/Reference:
Track Release Progress
As the project proceeds from sprint to sprint, your team will track the overall progress toward the next release. Your team will also track its progress to assess and improve its velocity. As your team tracks its progress, it should try to answer the following kinds of questions:
* (A) Are we working on the most appropriate user stories? Your product backlog will be refined with new user stories as the project progresses. However, if the total number of stories in the backlog is not decreasing, even though you are completing stories each sprint, the team should investigate the cause. The stories being completed might not be the best choices.
* (AB) Are we carrying technical debt? Some teams treat a user story as finished even though work such as fixing bugs remains to be completed. Those teams take on technical debt that they must pay later, usually at a higher cost.
BC: You can use work items to track and manage your work and information about your team project. A work item is a database record that Team Foundation uses to track the assignment and progress of work. You can use different types of work items to track different types of work, such as customer requirements, product bugs, and development tasks.
Reference: Visual Studio: Tracking Bugs, Tasks, and Other Work Items
