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.
B. The meeting must be kept short and well structured is an important feature of the daily stand-up / wash-up / Scrum meeting.
B. The meeting must be kept short and well structured is an important feature of the daily stand-up / wash-up / Scrum meeting.
See lessD. The entire team should attend the stand-up meetings.
A. Storming.
A. Storming.
See less
What 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 lessWhat is the exact meaning of a meeting having a time-box?
[D] The meeting can take no more than a maximum amount of time. --> Scrum uses time-boxed events, such that every meeting has a maximum duration. Timeboxing ensures that an appropriate amount of time is spent, minimizing the waste associated with open-end meetings without any time restriction. ScRead more
[D] The meeting can take no more than a maximum amount of time.
–>
Scrum uses time-boxed events, such that every meeting has a maximum duration. Timeboxing ensures that an appropriate amount of time is spent, minimizing the waste associated with open-end meetings without any time restriction.
Scrum events are using the following time-boxes:
For shorter Sprints, the events have a proportionately shorter time-box.
See lessResolving internal conflicts is NOT the responsibility of the Development Team.
[B] False --> An important asset of a Development team is self-empowerment, fostering self-organization. Hence, they are to manage their own work and themselves, which includes internal conflicts. Of course, the Scrum Master will monitor the handling of conflicts within the team but allows team mRead more
[B] False
–>
An important asset of a Development team is self-empowerment, fostering self-organization.
Hence, they are to manage their own work and themselves, which includes internal conflicts.
Of course, the Scrum Master will monitor the handling of conflicts within the team but allows team members to solve situations themselves first.
See lessWhat is NOT an attribute of the Development Team?
[A] Members of Development Teams are exchanged frequently to promote continuous learning and cross-functionality. -- Development Teams must have a constant composition over a longer period of time, in order to enhance the overall efficiency by learning and collaboration. Furthermore, constant changeRead more
[A] Members of Development Teams are exchanged frequently to promote continuous learning and cross-functionality.
—
Development Teams must have a constant composition over a longer period of time, in order to enhance the overall efficiency by learning and collaboration. Furthermore, constant changes in team composition makes it cumbersome to decide on an average capacity of Development Teams, a requisite for reliable project planning.
See lessOne of the benefits from Scrum is that the Development Team doesn’t have
[B] False -- One of the myths about Scrum is that it prevents you from writing detailed specifications. In reality, it is up to the Product Owner and the Development Team to decide how much detail is required, and this will vary from one backlog item to the next, depending on the insight and maturitRead more
[B] False
—
One of the myths about Scrum is that it prevents you from writing detailed specifications.
In reality, it is up to the Product Owner and the Development Team to decide how much detail is required, and this will vary from one backlog item to the next, depending on the insight and maturity of the team, among other factors.
Low-priority items have fewer requirement details, while high priority and “fine-grained items” tend to have more detail.
See less