Home » Microsoft » 70-498 » Which three actions should you perform?
Your development team uses the Microsoft Visual Studio Scrum 2.0 process template. You are the scrum master.
The product owner has created product backlog items and assigned them to a release.
You need to work with the development team to estimate when the release will be completed. Which three actions should you perform? (Each correct answer presents part of the solution. Choose three.)
A. Review the sprint backlog.
B. Review the product backlog with the Forecast option set to on to determine if the release can be completed based on the team’s velocity.
C. Have the team create tasks for each item in the product backlog and assign hour estimates to the task.
D. Review the sprint burndown chart.
E. Set each team member’s per day capacity.
F. Establish a sprint duration and a sprint velocity. Create enough sprints to complete the release.
G. Estimate effort for each item in the product backlog.
Correct Answer: BFG
Explanation/Reference:
B: By using the forecasting tool in Web Access, you can plan the number of Sprints it will take to complete a set of work. The forecasting tool is available only in the Product Backlog, not any of the Sprint Backlogs. Prior to being able to use the forecasting tool, your Product Backlog must have PBI and Bug work items already created with the effort specified.
You can turn on forecasting by clicking the Off hyperlink next to Forecast on the right side of the backlog page. The first time you do this, Web Access prompts you for the Velocity. Using your Development Team’s Velocity, Web Access will add a Forecast column and horizontal lines to the Product Backlog. In the Forecast column, it will display the Sprint that it predicts the PBI or Bug work item will be developed in.
Reference: Professional Scrum Development with Microsoft Visual Studio 2012 p.165
FG: If your team has completed multiple sprints, you can forecast release and product completion dates and plan future projects more accurately by reviewing the velocity report. Based on the velocity of previous sprints that the report illustrates, you can accomplish the following goals:
* 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.
Reference: Visual Studio, Velocity (Scrum)