A QA engineer wants to know what the team has committed to building in the current sprint. Which Scrum artifact should they consult?

• The Product Backlog — it contains everything the team plans to build ever — correct in theory, but the implementation handles this case differently
• The Increment — it shows what has already been completed
• The Sprint Backlog — it contains the items selected for this sprint and the team's plan for completing them
• The Definition of Done — it defines the quality standard for completion

A developer marks a story as "Done," but QA testing has not been completed. According to Scrum, what is the status of this story?

• Done — the developer is the primary owner of the story and their sign-off is sufficient
• Not Done — if the Definition of Done includes QA testing and it hasn't been completed, the story cannot be part of the Increment
• Done — "Done" means the code is written; testing is tracked separately
• In Progress — it should be moved back to the sprint backlog for the next developer to pick up

What is the purpose of the Definition of Done?

• A shared, explicit quality standard agreed by the whole team — if a story doesn't meet it, it cannot be counted as part of the Increment
• A document that describes what features the product owner wants in the next sprint — a popular misconception; the actual behaviour depends on the execution environment
• A legal contract between the development team and the client defining deliverables
• A checklist of technical coding standards maintained by the architecture team