A typical acceptance criteria is that a specific percentage of test cases passed and/or a specific number of critical defects unresolved. Yet the expressions have to be recognized as a way of the stakeholder to express the level of expected confidence. In other words “what are you OK with?” How can we help you gain confidence in the solution? What trends should we look for?
I have experienced situations where the solution was delivered, even though the criteria where not met. The so-called Go-NoGo meeting, was usually a Go-Go, and jokingly called so. I have also experienced that the business deferred a fix for a critical defect in production. That even if a planned release fulfilled the elaborate acceptance criteria – the delivery was cancelled. It was a major enterprise release that was technically to spec – yet because of other business risks, it was postponed.
As a tester you may experience this where all the automatic Factory Acceptance tests (FAT) pass, but the system still fails to react. I had to text “FAT failed” to someone recently, but it auto-corrected to “FART failed“. Indeed if all the requirements pass and but the system fails to deliver – it is a fart.
The challenge is that not everything that can be measured counts, and not everything that counts can measured.
And that’s not even considering that 100% testcases passed is a metric that makes no sense. Quality is not only the amount of specific attributes, as ISO/IEEE standards may lead you to measure, but a relationship “something that matters – to someone who matters – at sometime“. If you only look at the measurable – you miss half of the story.
The business needs
- fit for purpose (requirements) and fit for use (business context) [ITIL v3]
- to solve a business problem – ff the problem isn’t solved, the product doesn’t work. (Even of all the tests are green). [Ben Simo]
- information from testing to aid in making business decisions
Another problem with the traditional acceptance criteria is the amount of time and pressure that happens to a project to make sure they are met.
Many hours wasted on conference calls deciding if a bug was an S1 or S2 – and testers being hounded and harrassed as to whether a bug was a bug or not
LikeLike
[…] Acceptance criteria are more than what can be measured, An Expected Gathering […]
LikeLike
[…] errors (#bad, but it happens) – that contexts is also not good taking to the extreme. If the acceptance criteria is that X severity bugs can be released, gaming the play will leads us not to look for them. […]
LikeLike
[…] also: Acceptance is more than what can be measured, Testing is your sensory nerves, Eating wicked problems […]
LikeLike
[…] Related: Acceptance is more than what can be measured , You call that testing – how can that add value, […]
LikeLike
[…] Oredev have a majority of relevant tracks for the above business goals. But there may be other criteria – people for instance, cost and […]
LikeLike
[…] Related: DK om at udsætte sine behov, Weekend formula, That’s what friends are for, The 860 kcal bug, will work for LEGO, The yardstick of mythical normality acceptance is more than can be measured […]
LikeLike
[…] also: Acceptance criteria are more than what can be measured, Look for Minimum Viable Testing, Without Timing – Quality, Schedule and Cost […]
LikeLike
[…] Acceptance is more than what can be measured […]
LikeLike
[…] Acceptance is more than what can be measured […]
LikeLike
[…] we really measure when software is ready to ship? Jesper Lindholt Ottosen doesn’t think objective and quantifiable acceptance criteria tell enough of the […]
LikeLike
[…] Links: People are people – despite their labels, They are just people, The yardstick of mythical normality, Acceptance is more than what can be measured […]
LikeLike
[…] If you can establish the result of your solution in a deterministic, algorithmic and consistent way in a non-trivial problem, then you can solve the halting problem. But I doubt your requirements are trivial.. or even always right. Even the best business analyst or subject matter expert may be wrong. Your best oracle may fail too. Or you may be focussing on only getting what you measure. […]
LikeLike
[…] Every meeting had a check sheet, a resume form and a registration of preparation time. Because if it wasn’t measured it didn’t count. If it wasn’t in the play book it didn’t count […]
LikeLike
[…] is – oh, and the acceptance criteria of no severity 1-critical defects, is always negotiable. Acceptance of the delivery may be outside the test result… You always find things, you always choose […]
LikeLike
[…] could say… Still the pieces seem not to be 1-CRITICALLY missing, so the model is DONE and accepted. So even if the LEGO tester gets to ask “what if” – we have to remember to hear […]
LikeLike
[…] towards IEEE definition of delivering the expected. But even when he did, he failed to see that the unmeasured and irrational parts affected the value to the customer. I agree completely with The Cowboy […]
LikeLike