A single document, if that is what the Product Owner asked for

An increment of software with minor known bugs in it

Failing unit tests, to identify acceptance tests for the next Sprint

An increment of working software that is " done. "

The primary objective of the Sprint Retrospective is to identify what went wrong or hindered the Sprint

The primary objective of the Sprint Retrospective is to provide feedback to the Product Owner(s).

The primary objective of the Sprint Retrospective is to recommend ways to work better in the Sprint

Customer; Individuals

People; Relationships

Customers; Employees

Individuals; Interactions

The Sprint duration is extended

The tasks are determined to be unnecessary

They return to the product backlog

None of the above

Alphabetically first and then by list order in the Product Backlog

Grouped by business features first and then chronologically by date of original business request

Prioritized by business importance first. The items that result in biggest ROI, must be priorized first;

Chronologically by date of original business request first and then by list order in the Product Backlog