When “Five Minutes” Becomes a Requirement

This story was originally published on HackerNoon at: https://hackernoon.com/when-five-minutes-becomes-a-requirement.
Why precise requirements can be misleading when the underlying evidence is approximate, and how to trace a number back to its real basis.
Check more stories related to programming at: https://hackernoon.com/c/programming. You can also check exclusive content about #software-engineering, #requirements-engineering, #technical-documentation, #requirements, #product-management, #observability, #precision, #software-engineering-tips, and more.

This story was written by: @dietergoetz. Learn more about this writer by checking @dietergoetz's about page, and for more stories, please visit hackernoon.com.

A precise number is not necessarily precise knowledge. When an approximate observation becomes a hard requirement, false certainty is added to the specification.