05-07-2020, 11:13 AM
(05-07-2020, 10:09 AM)tomh009 Wrote: Requirements can be (and often are) a lot of work, and it's very tempting to take shortcuts. But you'll end up having to pay the piper later if you skip. Catching problems at the requirements stage is the least expensive option, doing it after release is the most expensive.
I agree entirely, just pointing out that even the most specific and precise requirements can still lead to bad outcomes. The process for developing requirements is just as important as having precise requirements.