Comments on: What Questions Do I Ask During Requirements Elicitation?

By: Martha Greenwood

Martha Greenwood — Sun, 20 Jan 2013 20:25:49 +0000

Agreed, Isabella…. I’ve found that if the client/stakeholder/CEO can list 5 of the most pressing issues with procedural functionality, that it is a great starting point for discussion and focus of the scope of engagement.

By: Martha Greenwood

Martha Greenwood — Sun, 20 Jan 2013 20:23:35 +0000

Great ideas, folks!

By: Martha Greenwood

Martha Greenwood — Sun, 20 Jan 2013 20:20:34 +0000

In reply to Laura Brandenburg.

Very insightful post, Laura.

I think the main fear of change though is fear of job loss. Many systems have built in redundancy, and streamlining an operation may mean loss of jobs/functions.

I too agree that change is in my blood, and seeing the ‘big picture’ is perhaps a talent, or perhaps the ability to simplify complex issues.

By: Laura Brandenburg

Laura Brandenburg — Mon, 27 Jun 2011 18:12:07 +0000

In reply to Chris. Great point Chris. These are nice additions. Though I do find that many stakeholders have trouble answering those questions directly it's good to be on the lookout for related information during your elicitation interviews and then follow-up to confirm those requirements.

By: Chris

Chris — Tue, 21 Jun 2011 09:38:40 +0000

I was re-reading the list and thought : why not extend the list to the non-functional and often implicit requirements as well?

So questions like : ‘how much’ (data, responsiveness (wait time) and ‘how secure’ might be added too.