Topic
8 articles tagged “process”.
The four common defect metrics that compare bugs found before and after a release are one fraction under different names. This guide gives the formulas with their sources, shows how a different denominator changes the answer, explains the time window, puts the often-quoted 85% average in context, and shows when a change between releases is real.
quality metrics · release · process
7 MIN
The two are constantly confused, and teams pay for it twice: quality rules copied into every story, or skipped entirely because everyone assumed they were somewhere else. This guide separates them, shows what belongs in each, and turns a Definition of Done into checks a pipeline enforces.
acceptance criteria · definition of done · process
8 MIN
Updated
The measured quality gap in AI-generated code is real but narrower than the headline, and it is not the interesting part. The interesting part is that review, testing, and traceability all assume the author understood what they wrote — and a product owner is the person who can put a name against each story before that assumption stops holding.
ai · code quality · product owner
6 MIN
A Definition of Ready stops half-formed work entering a sprint, and it also turns collaboration into a hand-off with an acceptance gate. Both are true. This guide covers when it helps, the failure mode that makes practitioners call it an anti-pattern, and the diagnostics that tell you which one you have.
definition of ready · process · product owner
6 MIN
How to run a go/no-go decision that can genuinely say no: one named owner instead of a group vote, evidence gathered before the meeting, criteria with thresholds written in advance, every accepted risk carrying an owner and an expiry, and escaped defects measured afterwards to correct the criteria.
release · product owner · process
8 MIN
Updated
Support data is the earliest external signal that a release went wrong, and most of it gets read as a support-team scorecard instead. This guide separates the metrics that say something about the product from the ones that say something about the queue, and gives a weekly routine for turning volume into defects.
quality metrics · product owner · support
7 MIN
A practical guide to test cases: what to include, three techniques for choosing inputs, ten real cases for a checkout form with the results we observed, and how the cases become an automated test. Three of the ten raised questions the form's requirements don't answer.
qa · test cases · process
8 MIN
Updated
We found a real bug in a practice shop and wrote it up two ways. The difference between 30 and 100 points is steps, expected versus actual, environment, reproducibility, and evidence. Each part is explained with the exact lines from the report.
qa · bug reporting · process
8 MIN
Updated