“Requirement” is an empty word.
“Requirement” is an empty word. It’s overused and it does mean different things for different people.
Take a problem, P, with a requirement, R in a software engineering context.
If I say something R is a requirement to solve P, everyone would think that:
I know what I am doing.I know what I want.I simply narrowed the solution space because I have forced everybody to take the narrow perspective of the requirement R of the overall problem P.
It’s a “requirement” after all. I do “require” it. Or the company does “require” it. Or the customer does “require” it. It’s nearly a non-negotiable.
The more senior you are, the more people will see a “requirement” as “commandment.” You have your holy text with you that no body should or can question.
Avoid it at all cost unless you’re 100% sure that something is truly required. Keep the solution space open with User Stories and Narratives instead. We use this in all our [Product/Technical] tickets on Asana in SpatialX.
Salam, Peace.
