Business & Finance
Share
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.
Who 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 lessWhat are the major properties of a cross-functional Development Team?
[B] The team has all the skills on board, needed to accept collective ownership for the next product increment. -- Development Teams are cross-functional, with all of the skills as a team necessary to create a product increment. Development Teams do not contain sub-teams dedicated to particular domaRead more
[B] The team has all the skills on board, needed to accept collective ownership for the next product increment.
See less—
Development Teams are cross-functional, with all of the skills as a team necessary to create a product increment. Development Teams do not contain sub-teams dedicated to particular domains like testing or business analysis.
Please select which statement with respect the Refinement is the MOST accurate
[A] Refinement is a part-time activity during a Sprint between the Product Owner and the Development Team. - Product Backlog Refinement is the act of adding detail, estimates, and order to items in the Product Backlog. This is an ongoing process in which the Product Owner and the Development Team coRead more
[A] Refinement is a part-time activity during a Sprint between the Product Owner and the Development Team.
–
Product Backlog Refinement is the act of adding detail, estimates, and order to items in the Product Backlog. This is an ongoing process in which the Product Owner and the Development Team collaborate on the details of the Product Backlog items.
Refinement usually consumes no more than 10% of the capacity of the Development Team. During Product Backlog Refinement, items are reviewed and revised, based on feedback from the Development Team and possibly other stakeholders or experts.
However, items can be updated at any time by the Product Owner or at the Product owner’s discretion
See lessWhich of the following options is NOT true about Scrum?
[D] Changing Scrum Masters midstream a project will encourage self-empowerment of the Development Team. The Scrum Master is the servant-leader and coach of the Development Team, promoting an atmosphere of mutual respect and trust among the Development Team members. Changing Scrum Masters sometime inRead more
[D] Changing Scrum Masters midstream a project will encourage self-empowerment of the Development Team.
The Scrum Master is the servant-leader and coach of the Development Team, promoting an atmosphere of mutual respect and trust among the Development Team members. Changing Scrum Masters sometime in a project is very disruptive for the Development Team, and will not contribute to self-empowerment of the Development Team.
See lessWhat action will the Development Team take when it is discovered that…
[A] The Development Team adds the new work to the Sprint Backlog. As new work with respect to the agreed-upon sprint goal is required, the Development Team adds it to the Sprint Backlog. Only when large amounts of new work appear to be needed (which will jeopardize the overall Sprint goal), the ProdRead more
[A] The Development Team adds the new work to the Sprint Backlog.
As new work with respect to the agreed-upon sprint goal is required, the Development Team adds it to the Sprint Backlog. Only when large amounts of new work appear to be needed (which will jeopardize the overall Sprint goal), the Product Owner is consulted to discuss the situation. As work is performed or completed, the estimated remaining work is updated. When elements of the plan are deemed unnecessary, they are removed. Only the Development Team can change its Sprint Backlog during a Sprint. The Sprint Backlog is a highly visible, real-time picture of the work that the Development Team plans to accomplish during the Sprint, and it belongs solely tot the Development Team. The Product Backlog is owned by the Product Owner, so the Development Team cannot add work to the Product Backlog by itself.
See lessScrum Teams should normalize their estimates
[B] False When normalization implies ‘commoditization’ of story points, it can skew people's ideas of what constitutes value. The point of departure is that the measure of productivity in Scrum should always be the delivery of working increments. Therefore, such normalization is considered a bad ideRead more
[B] False
When normalization implies ‘commoditization’ of story points, it can skew people’s ideas of what constitutes value. The point of departure is that the measure of productivity in Scrum should always be the delivery of working increments. Therefore, such normalization is considered a bad idea in principle – and so answer B is correct. However, although story points estimates should not by used by management as a productivity measure, the normalization of estimates can be useful in practice, especially when multiple teams are working on the same product backlog.
See less