Your development team uses the Microsoft Visual Studio Scrum 2.0 process template. The team has identified items from the product backlog for the next sprint. You need to ensure that the team has…

Question

Options

• AReview the sprint Burndown chart.
• BHave the team assign hour estimates to each sprint task.
• CReview the sprint backlog.
• DAssign story points to each item in the product backlog.
• EReview the product backlog with forecast set to On to determine if the sprint can be
• FSet each team member's per day capacity.

• A
  6% (3)
• B
  4% (2)
• C
  79% (38)
• D
  10% (5)

Explanation

Sprint Burndown charts can show the team how much work remains in the Sprint. These charts will often include an ideal trend line. This line represents the ideal rate at which the Development Team is able to complete all of the remaining effort, at a constant rate, by the end of the Sprint. Professional Scrum Development with Microsoft Visual Studio 2012 p.283 Prior to the Sprint, there shouldn't be any Task work items in the Sprint Backlog. Ideally, the Development Team creates its tasks during the Sprint Planning meeting and not before. Professional Scrum Development with Microsoft Visual Studio 2012 p.175 The Sprint Backlog contains those items selected by the Development Team plus a plan for delivering them. The Sprint Backlog shows the work remaining in the Sprint at all times. Professional Scrum Development with Microsoft Visual Studio 2012 p.4 Story points should be already assigned to PBIs during identification for the sprint.

No community discussion yet for this question.