INTRODUCTION TO SOFTWARE ENGINEERING
AGILE SOFTWARE DEVELOPMENT
|
Question
[CLICK ON ANY CHOICE TO KNOW THE RIGHT ANSWER]
|
As part of the Estimate Activity Durations process, the project manager facilitates a sprint planning meeting with the product owner and Scrum team. The project manager breaks down the user stories into low-level tasks, estimates the time required in hours, and determines the sprint backlog based on the team’s capacity. Despite meticulous planning, the sprint fails.What might the project manager have done differently?
|
|
Asked the team to prioritize the product backlog before determining the sprint backlog
|
|
|
Assigned the identified low-level tasks to specific individuals in the project schedule
|
|
|
Empowered the team to determine how many user stories they can complete during the sprint
|
|
|
Used story points instead of hours while estimating the size of the user stories and tasks
|
Explanation:
Detailed explanation-1: -In Scrum Projects, Estimation is done by the entire team during Sprint Planning Meeting. The objective of the Estimation would be to consider the User Stories for the Sprint by Priority and by the Ability of the team to deliver during the Time Box of the Sprint.
Detailed explanation-2: -Sprint planning is limited to a maximum of eight hours. The general rule of thumb is to allow two hours of sprint planning for every one week of sprint length. That means teams should timebox sprint planning to four hours for a two-week sprint and eight hours for a one-month sprint.
There is 1 question to complete.