Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
How many Iterations would it take for a team with a velocity of 20 story points…
C. 3 Iterations.
C. 3 Iterations.
See lessWhat are the two inputs to PI Planning?
A. Vision and D. Top-10 Features list are the two inputs to PI Planning.
A. Vision and D. Top-10 Features list are the two inputs to PI Planning.
See lessWho participates in the backlog refinement event?
D. The Agile Team members and other Subject Matter Experts participate in the backlog refinement event.
D. The Agile Team members and other Subject Matter Experts participate in the backlog refinement event.
See lessThe three pillars of Scrum are transparency, inspection, and what else?
B. Adaptation.
B. Adaptation.
See lessIn the context of a Team Increment, every Iteration each team plans, builds, tests, integrates, and?
B. Review their work. In the context of a Team Increment, every Iteration each team plans, builds, tests, integrates, and
B. Review their work.
In the context of a Team Increment, every Iteration each team plans, builds, tests, integrates, and
See lessWhy is it important to organize the work for Iteration Planning?
C. So a realistic work scope can be defined.
C. So a realistic work scope can be defined.
See lessWho defines the final scope of a committed Iteration?
A. The Agile Team.
A. The Agile Team.
See lessWhat is the goal of a Sprint Retrospective?
[B] Refinement of epics nominated by the Product Owner for the next couple of sprints, in order to promote reliable release planning. [C] Verification of how well the product increment satisfies the applicable user stories in the Product Backlog. --> The Sprint Retrospective is an opportunity forRead more
[B] Refinement of epics nominated by the Product Owner for the next couple of sprints, in order to promote reliable release planning.
[C] Verification of how well the product increment satisfies the applicable user stories in the Product Backlog.
–>
The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for identified and agreed-upon improvements to be enacted during the next Sprint(s).
Thus, the Sprint Retrospective provides a formal opportunity to focus on inspection and adaptation.
Refinement of epics is part of the regular grooming exercise under auspicien of the Product Owner, and is not part of the retrospective.
Only during Sprint Review, it is determined whether the product increment satisfies the applicable items on the Product Backlog according to the ‘Definition of Done’.
See lessThe Product Owner role and Scrum Master role are never included …
[B] False --> The Product Owner and Scrum Master roles are not included in the Development Team size count unless they are also executing the work of the Sprint Backlog. Although in the majority of cases they are not part of the Development Team, the Product Owner and/or the Scrum Master can be (Read more
[B] False
–>
The Product Owner and Scrum Master roles are not included in the Development Team size count unless they are also executing the work of the Sprint Backlog.
Although in the majority of cases they are not part of the Development Team, the Product Owner and/or the Scrum Master can be (part-time) included in the Development Team size count.
See lessWho is responsible for updating the estimates of the work during a Sprint?
[A] The Development Team --> At any point in time in a Sprint, the total work remaining in the Sprint Backlog items can be summed. The Development Team tracks the total work remaining at least for every Daily Scrum if needed after a re-estimate of tasks to be done. Hence the estimates for the remRead more
[A] The Development Team
–>
At any point in time in a Sprint, the total work remaining in the Sprint Backlog items can be summed. The Development Team tracks the total work remaining at least for every Daily Scrum if needed after a re-estimate of tasks to be done.
Hence the estimates for the remaining work are updated on a daily basis. Note that Scrum does not consider the time spent working on Sprint Backlog Items. The work remaining and date are the only variables of interest.
See less