Artifacts
⏱ ~3-min readAceMark GuideWhat this topic is really about
The Definition of Done is a shared agreement created by the entire Scrum Team to ensure transparency and consistent quality, and it must also respect any organizational or regulatory standards. It is not authored solely by the Product Owner (option A) because the PO lacks the development perspective needed to define completion criteria.
The Increment is the sum of all completed Product Backlog items in a Sprint and must be usable, meeting the Definition of Done, which makes it production‑ready. It does not require explicit customer approval; the Scrum Team declares it done, so option B is a misconception that confuses acceptance criteria with formal sign‑off.
See the mechanism
Velocity is a useful, complementary metric that teams can opt to use for forecasting, but it is not a mandated Scrum artifact. A diagram for this topic isn't available yet — the worked example below walks the same reasoning step by step.
An exam-style question, fully explained
Velocity is:
- Identify what the question tests: Velocity is:.
- Velocity is a useful, complementary metric that teams can opt to use for forecasting, but it is not a mandated Scrum artifact.
- It is incorrect to view it as a required metric or something set by the Scrum Master, as Scrum focuses on delivering valuable increments rather than enforcing specific estimation metrics.
Traps the examiner sets
- It is incorrect to view it as a required metric or something set by the Scrum Master, as Scrum focuses on delivering valuable increments rather than enforcing specific estimation metrics.
- The Scrum Master may coach the event but does not own it; choosing A is a common trap that confuses the facilitator role with responsibility.
Test your recall
Answer each from memory — you'll see instantly whether you're right and why.
Run a focused 10-question mini-mock on Artifacts and see it stick.
Practice more of this topic →