So, What is Requirements Work?
Interesting article from the Spring Issue of IEEE Software
entitled, “So, What is Requirements Work?”
. The author, an obvious expert in the field, goes on to conclude that Requirements Work is basically helping people help themselves. I like this definition. As a Requirements Analyst, you cannot know every single domain you will be parachuted into as your career progresses. No one can be an expert in Medicine, Law, Accounting, Botany, etc. Instead, “smart” Requirements Analysts depend on the domain experts that already exist to guide them to the problems that need to be solved. Then, they are able to get out of domain experts/stakeholders the specifications of those problems. Finally, the requirements analyst can specify those requirements in formats that are decipherable by multiple stakeholders (developers, customers, etc.).
I’m not sure I agree that Requirements Work involves coming up with solutions though. It seems to violate some central core of Requirements that were taught to me, “Concentrate on the problem, not the solution.” But, I’ll admit as a former software developer, I can’t help to think of solutions when I hear problems. I have to be judicious, though, about when I bring them up.
Check the article out yourself when you get the chance!