The Development Team should not be interrupted during the Sprint. The Sprint Goal should remain intact. These are conditions that foster creativity, quality and productivity. Based on this, which of the following is FALSE

Why are you confused? The question asks you to identify which answer is false, and B is indeed the only one that is false. D is perfectly valid.

My doubt is:

At the sprint planning we define the sprint goal, it is related to the sprint backlog. If i negociate the sprint backlog with the product owner, it can change my sprint goal ? i was reading contents today, saying that the sprint backlog can't be changed.

I need to clarify more about this.

Thank's Ian Mitchell

Development team can add more product backlog items which are related the current sprint's, sprint goal.
Actually sprint goal is created in order to give theam more flexibility regarding the functionality that can be implemented during the sprint. This flexibility can be achieved in case development team finds that more PBI's can be inculded in the current sprint.

Thank's Nipun,

my doubt appeared when i did this simulate:

The Development Team realizes that the volume of work of one of the items in the
Sprint Backlog is estimated incorrectly, and the current volume of work of the whole
Sprint Backlog is 130 instead of 100. What should we do?

A. They should return some items back to the Product Backlog to keep the Sprint
Backlog volume to about 100 points
B. They should ask Scrum Master for more time for this current Sprint
C. They should ask Product Owner to decide on this
D. They shouldn’t do anything now

I answered the C option, following the scrum guide the dev team negociate with the product owner to add os remove itens, but the simulare says that the right answer is the D option, them i can understand that the simulate is wrong ?

Thank's all, i'm studying to take my psm certification as soon as possible

Dear All,

Below my answer is as per my knowledge on Scrum and Agile

Point-1: Scrum just not allow addition of any new PBI (Product Backlog Item), if it put the sprint goal in danger. but if development team all agree to add new PBI to the sprint goal and sure of completing it, can can do so after discussion with the PO.

In the same way they can replace a PBI (Add a new PBI and Remove another PBI having equal weight) if some thing urgent comes out from client or stack holder.

Point-2: Sprint Back log is a changeable item through out the sprint , it can grow from 100 story point (Task) to 120 or 130. This happen for complex PBI, when the team not able to analyse all possible story point in the sprint planning meeting.

Generally best team find a way to complete the additional work, if they can't able to compete all, they can discuss with PO , to move the incomplete PBI back to the PBI list for next iteration.

Hello all, can someone please explain to me why this answer chosen (A) by scrum.org is correct. i am confused. i thought the sprint backlog does not not change during sprint. I choose C but scrum says the correct answer is A.

The Developers should not be interrupted during the Sprint and the Sprint Goal should remain intact. These are conditions that foster creativity, quality and productivity.

(Which one the following answers is FALSE?)

A.The Sprint Backlog is fully formulated in the Sprint Planning event and does not change during the Sprint.

B. The Developers may work with the Product Owner to add or remove work if they find themselves with more or less capacity than expected.

C.As a decomposition of the selected Product Backlog items, the Sprint Backlog changes and may grow as the work emerges.

D.The Product Owner can help clarify or optimize the Sprint when asked by the Developers.

What does the Scrum Guide say about the Sprint Backlog?

To help you answer @Timothy's question.  This comes from the Scrum Guide's section that describes the Sprint Backlog. The emphasis was added by me for clarity.

The Sprint Backlog is a plan by and for the Developers. It is a highly visible, real-time picture of the work that the Developers plan to accomplish during the Sprint in order to achieve the Sprint Goal. Consequently, the Sprint Backlog is updated throughout the Sprint as more is learned. It should have enough detail that they can inspect their progress in the Daily Scrum.

I am not sure where you got your information that the Sprint Backlog cannot change. I do not remember the Scrum Guide ever stating that. It has always described it as fluid based upon new knowledge obtained. The same holds true for the Product Backlog. 

The Sprint Backlog is fully formulated in the Sprint Planning event and does not change during the Sprint.

One of Scrum's Top 10 Myths!

i thought the sprint backlog does not not change during sprint

That would be an odd commitment to make when developing a complex product. A Sprint Goal would be a better one, and to have a forecast of work which can be inspected and adapted.

"Consequently, the Sprint Backlog is updated throughout the Sprint as more is learned."

In

Scrum guilde 

and 

Sprint Goal: a short expression of the purpose of a Sprint, often a business problem that is addressed. Functionality might be adjusted during the Sprint in order to achieve the Sprint Goal.

in Scrum Glossary

So question is which conclusions are correct?. After many years so many infomations update wrongly make me confuse while i study  PSPO course at other website. Even in this Scrum.org site, people also have conflict with these Myths, Glossary.  That was ridiculous