Embed Notice

@inthehands My definition of "requirement" is a thing that, if it were impossible to deliver, we would cancel (or at least seriously reconsider) the project. If its impossibility causes the "requirement" to vanish, then it was never IMO a requirement.

BUT! devs often forget that minimally delivering just the "requirements" may still result in a worthless product, and the goal is a worthy product. Checklist-obsession is not useful. The goal is to delight; not barely meet "requirements."