Q:
Why is it suggested that story point values be chosen from a Fibonacci sequence?
Q:
Suppose completing user story A is estimated to be 2 story points. Relative to that, completing user story B is estimated to be twice the effort. How many story points are needed to complete both user stories? Use a Fibonacci number for each user story estimate.
Q:
Within a sprint, suppose a user story estimated at 13 story points is partly completed. The developers say the work for it is half done. How many story points would the partial work contribute toward their velocity for the sprint?
Q:
A development team estimates their velocity to be 15 story points per sprint, based on data from a similar project with the same developers, type of software product, and sprint duration. For the current project, after the first few sprints, their actual velocity was calculated to be 12 story points per sprint. What should be done for the next sprint?
Q:
A development team is planning their fourth sprint, and have three prior sprints of actual velocities. To estimate their velocity for the upcoming sprint using this data, what issues should their estimation technique address? Choose the 2 that are correct.
Q:
Suppose there is a project for a software product with an inception phase followed by 5 development sprints, ending with a target date to present the product at a trade show. What needs to be flexible to apply Scrum to plan this project?
Q:
Besides task planning, how can Gantt charts be adapted to do release planning? Choose the 2 that are correct.
Q:
Release planning considers the priorities of the user stories in the product backlog, where “should do” means ___, and “could do” means ___.
Subscribe
0 Comments
Find Questions in This Page: "CTRL+F"
