Array

Getting to Functional Requirements, part 1 – the never-ending open-ended question…

Back to the nasty question – what sort of Information System shall will we build?

“What sort of system do you want?”
“hmmm, one that processes all our customer orders, I think. What do you think, George?”
“Well Fred, I suppose so, but I know it has to be fast, and run 24/7.”
“OK………(???)”

We already know the problem with asking people what they want, but it is even worse than you think, because it's an open-ended question; and the problem with open-ended requirements questions is determining when the question has been fully answered. How do you know you have all the requirements? Well, you don't.

Wait, it gets worse! How do you know if the requirements you did get are relevant? If any of them are duplicates? If any of them contradict other requirements? Again, you don't.

So you need a different question. When you ask people what they want, you can get blank stares in return… but, if you ask people what they do, you will get all their knowledge and expertise in return; and that is where the requirements will come from… look for part 2 tomorrow…

Would you recommend this article?

Share

Thanks for taking the time to let us know what you think of this article!
We'd love to hear your opinion about this or any other story you read in our publication.


Jim Love, Chief Content Officer, IT World Canada

Featured Download

IT World Canada in your inbox

Our experienced team of journalists and bloggers bring you engaging in-depth interviews, videos and content targeted to IT professionals and line-of-business executives.

Latest Blogs

Senior Contributor Spotlight