Feature versus requirement

One of the most common mistakes made on a project is to seize on a feature and call it a requirement without first understanding the problem and the expectations around a solution

Subscribe to Think.Forget.Do

Sign up now to get access to the library of members-only issues.
Jamie Larson