Which of the following are true about the length of the Sprint? (Choose two.)

• A.Sprint length is determined during Sprint Planning, and should hold the time it will take to code the
  planned features in the upcoming Sprint, but does not include time for any testing.
• B.All Sprints must be 1 month or less.
• C.It is best to have Sprints of consistent length throughout a development effort.
• D.Sprint length is determined during Sprint Planning, and should be long enough to make sure the
  Development Team can deliver what is to be accomplished in the upcoming Sprint.
• E.The length of the Sprint should be proportional to the work that is done in between Sprints.

Comment: *

Name: *

Email: *

Verification: *

If two Scrum Teams are added to the development of a product that previously had only one Scrum Team, what will be the immediate impact on the productivity of the original Scrum Team? (Choose the best answer.)

• A.Its productivity is likely to decrease.
• B.Its productivity is likely to increase.
• C.Its productivity is likely to stay the same.

Comment: *

Name: *

Email: *

Verification: *

Where are two good ways for the Development Team to make non-functional requirements visible?
(Choose two.)

• A.Put them on a separate list on the Scrum board, available for all to see.
• B.Run the integration and regression tests before the end of the Sprint, and capture the open work for the
  Sprint Backlog of the next Sprint.
• C.Add them to the definition of "Done" so the work is taken care of every Sprint.
• D.Run the integration and regression tests before the end of the Sprint, and capture the open work for the
  Sprint Backlog of the next Sprint.
• E.Add them to the Product Backlog and keep the Product Owner posted on the expected effort.

Comment: *

Name: *

Email: *

Verification: *

You have six teams using a traditional method to deliver a product. Your management has asked you to start using Scrum. In the initial project there were separate plans and teams for the layers of a software system, i.e. one for the front-end, one for the middle tier, one for the back-end, and one for the interfaces and services. This resembles what is known as component teams. But you have read that it's a good idea to have teams organized by feature.
What are the advantages of keeping component teams while starting Scrum?

• A.There's less initial disruption than organizing into new teams. As they start, they will discover what works best, and how to potentially re-organize towards this.
• B.There are fewer cross-team dependencies than working in feature teams.
• C.Because they have worked together for some time, they are likely able to start producing shippable Increments faster that new feature teams would.
• D.Component teams generally have the skills needed to create a working Increment of software that provides business value.

Comment: *

Name: *

Email: *

Verification: *

When is a Product Backlog item considered complete? (choose the best answer)

• A.When the item passes ail acceptance criteria
• B.When the item has gamed product sponsor approval
• C.At the end of the Sprint
• D.When the item meets the Definition of Done

Comment: *

Name: *

Email: *

Verification: *