Requirements are the key to getting a good solution, whether in procurement or just choosing between options. Most people get their requirements wrong, largely because they haven't drawn this connection. Requirements analysis is the first stage in the systems engineering process and software development process. Systems Engineering Fundamentals Defense Acquisition University Press, 2001 (Photo credit: Wikipedia) Common Mistakes This list isn't exhaustive, I'm sure there are many more ways that requirements can go wrong. having too many not prioritising not engaging end users to develop requirements that meet their needs just throwing everything in that users ask for, without analysis of necessity (the big stapler approach) having requirements that constrain options to a specific solution ( "we need to upgrade Oracle" rather than "we need a database"). I've spent years as an analyst, and leading teams of business analysts, coming up with requirements…
Continue Reading