Answer: Probably no — quality was not truly built in.
The team may have done some testing, but the result shows that quality was not built into the full process.
Why?
Because:
| Evidence | What it suggests |
|---|---|
| Checkout crashes 40% of the time | Critical functionality was not properly tested. |
| Password reset fails | Important user flow was missed. |
| Buttons do not respond on mobile | Mobile/responsive testing was missing. |
| All stories were marked Done | The Definition of Done was probably weak. |
| Automated tests passed | The automated tests did not cover the right scenarios. |
Teaching explanation
You can tell students:
“If all stories were marked Done and automated tests passed, but customers still experience major failures, then the team did not build quality deeply enough into the process. They may have tested something, but not the right things.”
What was missing?
Likely missing items:
| Missing quality practice | Example |
|---|---|
| Strong Definition of Done | Story cannot be Done unless tested on desktop and mobile. |
| Better acceptance criteria | Checkout must work successfully for valid payment, failed payment, and mobile checkout. |
| End-to-end testing | Test the complete user journey: login → order food → checkout → confirmation. |
| Mobile testing | Buttons and screens must work on common mobile screen sizes. |
| Regression testing | Existing features like password reset must still work after new changes. |
| Exploratory testing | Humans try unusual cases that automation may miss. |
Best short classroom answer
No, quality was not truly built in. The team had a “Done” label and automated tests, but the tests and DoD were incomplete. Built-in quality means the team prevents defects through strong acceptance criteria, testing, review, mobile checks, and Definition of Done before the work is released.
A good discussion follow-up:
“What should be added to the Definition of Done so this problem does not happen again?”
From AI Tools as is
