Quality culture grows through daily practices, not occasional big initiatives. Small, consistent behaviours—such as how code reviews are done or how bugs are discussed—can either strengthen or weaken quality thinking.
Everyday Practices that Support Quality
Examples include asking “How will we test this?” in refinement, adding acceptance criteria that cover both functional and non-functional aspects, and using pair testing or mob testing for complex features. Consistent retrospectives that examine both successes and failures also build learning habits.
# Practical quality-supporting practices
- Include testability and observability in design discussions.
- Use code reviews to discuss risks, not just style.
- Regularly review flaky tests and fix root causes.
- Share small lessons learned from incidents or near-misses.Visualising work, such as using boards that highlight blocked items or quality-related tasks, makes quality visible and easier to discuss. This helps prevent quality work from being hidden behind generic “done” columns.
Balancing Speed and Quality
Healthy cultures recognise that speed and quality are not always in conflict; investing in quality practices often increases sustainable delivery speed. The key is to make trade-offs explicit rather than accidental.
Common Mistakes
Mistake 1 — Introducing too many practices without feedback
People feel overloaded.
❌ Wrong: Adding multiple checklists, meetings, and tools at once.
✅ Correct: Experiment with a few practices, gather feedback, and iterate.
Mistake 2 — Leaving practices undocumented
New team members struggle.
❌ Wrong: Relying on oral tradition for how quality is handled.
✅ Correct: Capture key practices in lightweight guides or onboarding materials.