Enough to deploy the increment and update the product backlog based on the outcome of the sprint review

Enough to clean up lingering definition of done points

None, a new sprint starts immediately after the end of the previous one

At most a week for a one-month sprint

The degree to which the system under test has been exercised by tests.

The number of Developers that understand how the code works.

An insurance policy that covers the code for defects.

The percentage of code in version control included in a build.

A term representing the eventual consequences of poor technical choices

Developers that have to pay college debt

Code that hasn’t been documented

The money an organization owes to tool and hardware vendors

However much time the developers ask the PO to be present

40%, or more depending on stakeholders

100%

Enough to be aware of the increment’s value at the sprint review

Inform the product owner and the stakeholders during the sprint review

As soon as they realize they should work with the product owner to remove some work while not endangering the sprint goal

Outsource the work to another team

Use a definition of done with lower standards to be able to finish all the work they committed to

True

False

Code review is done

Acceptance tests pass

Regression tests pass

The product is released at the end of every sprint

Code coverage 90%

Work with the QA departments on the increment of the current sprint

Update the project plan with stakeholders

Refine the backlog

There are no such activities. The next sprint starts immediately after the current sprint

typically 10 or fewer people

this differs every sprint

at least 8 people

3 to 11

It defines a state when the entire Increment is releasable.

It might be a subject of discussion during the Sprint Retrospective.

It is synonymous with acceptance criteria.

It is the sole responsibility of the Developers to define it.

It can only be extended; nothing can be removed.