How much of Quality Beyond Correctness is about the implied acceptance criteria?

This question is taken from the AMA about quality beyond correctness, and comes from Dan Caseley.

I totally agree - it's not practical or desired to list every acceptance criterion for every piece of work.  There are, however, a number of heuristics we can use, one of which is quality characteristics.  Through something like a RiskStorming workshop, teams and project members can agree on the most important aspects of quality that they want to focus on for x period.  Say that user friendliness and performance are two of the ones picked.  When testing, designing, prototyping, etc., we can ask ourselves:

By agreeing on the most important quality characteristics and focussing down on them, you already have buy-in from the team / project that these things are important and should be addressed.  It also helps us to prioritise and focus our testing efforts, since we also know that we can't test for everything, but we can start with what we've agreed is the most important.

Thanks for your question, Dan!

Find all the questions and answers to this AMA in the AMA About Quality Beyond Correctness collection.