Kano is not in the Foundation Level syllabus. The decay of delight still wrecks roadmaps.
Kano’s categories are an external convention. What matters in practice is that last year’s delighter is this year’s unspoken expectation.
7 min read
Articles
Your requirement isn't non-functional. It's a quality requirement or a constraint, and they behave nothing alike
Calling something non-functional hides whether you can measure it or whether you have already removed options from the solution space.
8 min read
Three lines, one meeting: system boundary, context boundary and scope are not synonyms
A team can agree a drawing and still be arguing three different questions. Separate the lines before you negotiate the change.
7 min read
Validation is not review, and your review is not validation
A clean review record can still leave you solving the wrong problem. Validation asks a different question, with different evidence.
8 min read
Writing Good Acceptance Criteria
A short guide to acceptance criteria that actually catch problems.
1 min read
Why Acceptance Criteria Fail Late
Most acceptance criteria are written after the argument they were meant to prevent.
1 min read