It seems that no matter where I go, no one have a clear understanding of what a requirement is and is not?
Is it really that hard to define considering there is even standards for it, or is it that requirements are just not a priority in most companies....and that is because they are "Agile"?
It seems that no matter where I go, no one have a clear understanding of what a requirement is and is not?
Is it really that hard to define considering there is even standards for it, or is it that requirements are just not a priority in most companies....and that is because they are "Agile"?
Link to comment
https://beta.jimiwikman.se/forums/topic/1840-why-is-requirements-so-difficult-to-define/Share on other sites