Want to write better acceptance criteria? π€
Acceptance criteria often describe functional requirements. But other requirements could be as important for the chosen solution.
π‘Tip: Enrich acceptance criteria with non-functional requirements
βWhat are non-function requirements?
Non-function requirements are quality attributes. Every developer (should) thinks about these when implementing a feature. You’re helping the team to choose the better solution by adding them.
Quality attributes reflect levels of service such as:
– performance, scalability, and availability
– security
– disaster recovery
– accessibility
– monitoring, management, and audit
– flexibility and extensibility
– maintainability
– legal, regulatory and compliance
– internationalization and localization
π Write them as a checklist π
Example: π
– The screen loads within 3 seconds.
– Change should be reflected on the website within 15 minutes.
– Navigation is intuitive and user-friendly.
– Help tooltips are provided on the feature.
– Error messages are clear and informative.
Try this tip next time you’re writing acceptance criteria π
Do you have tips for writing better acceptance criteria?