What problems did you run into while gathering requirements?

Questions by SonaliB   answers by SonaliB

Editorial / Best Answer

andar777  

  • Member Since Aug-2007 | Aug 30th, 2007


Helping users to explain their requirements.


First and for most, you must understand that for the most part, users do not understand what is happening behind the forms they are inputting data into.  A Business Analyst needs to be able to view the system through the eyes of a user and though the eyes of the developer.  Then negotiate a compromise that will meet the user’s needs and also maintain system integrity.   

You have to peel back the onion with the users by asking leading questions, such as, If you select this value from the list box, what would you like to see happen on  the screen. 

If you forget about the code and focus on the behavior of the form, you'll get a lot further with users.  In addition, users tend to get there backs up when they are approached by someone from IT because they tend not to feel that the IT rep understands what they are saying and they get very frustrated.  If they are frustrated, then gathering solid requirements goes out the door.

I was a user before I became a BA and I'm proud of it.  :-)

Showing Answers 1 - 0 of 0 Answers

Freejesh

  • Dec 5th, 2006
 

Problems faced while gathering Customer Requirements.

Communication problem.

Inconsistent or contradictory statements which leads to delay.

Difference in Industry Knowledge.

Note: Above mentioned factors can be controled if same process is followed by the vendor as well as the Client.

Naz

  • May 21st, 2007
 

1- lack of consolidated business decision for To Be business processes.
2- This can be controlled by defining roles and responsibilities of project team members and proper communications.

  Was this answer useful?  Yes

Pashu Pati Nath Pandey

  • Jul 27th, 2007
 


The problem are;

@ Absence of System thinking
@ Proper method of gather of data or observation
@ proper reflection of situation
@ Proper interpretaion of the data gathere

Any how care should be taken to check that any factor other factor under normal circumstances are not present.

  Was this answer useful?  Yes

andar777

  • Aug 30th, 2007
 

Helping users to explain their requirements.


First and for most, you must understand that for the most part, users do not understand what is happening behind the forms they are inputting data into.  A Business Analyst needs to be able to view the system through the eyes of a user and though the eyes of the developer.  Then negotiate a compromise that will meet the user’s needs and also maintain system integrity.   

You have to peel back the onion with the users by asking leading questions, such as, If you select this value from the list box, what would you like to see happen on  the screen. 

If you forget about the code and focus on the behavior of the form, you'll get a lot further with users.  In addition, users tend to get there backs up when they are approached by someone from IT because they tend not to feel that the IT rep understands what they are saying and they get very frustrated.  If they are frustrated, then gathering solid requirements goes out the door.

I was a user before I became a BA and I'm proud of it.  :-)

There could be a lot of problems while gathering requirements these are some up to my knowledge
1) Contradiction ( As different S/H or different ideas from same s/H)
2)Communication.
3) Undocumented process
4) Lack of access to en users
5) Instability and end users]
6) Abunance of choice to s/H or end users
7)s?H design
8) Bad requirements

GBBASY

  • Jul 13th, 2008
 

1.Dependencies on thrid party interface
2.Analyzing all possible secenarios
3.Impact on current system behaviour

  Was this answer useful?  Yes

dody1108

  • May 14th, 2010
 

  • Difference of opinions between business users
  • Frequent changes in requirements, business rules
  • Undocumented business rules
  • Managing number of requirements within available time frame

  Was this answer useful?  Yes

himansnu gaur

  • Oct 11th, 2011
 

The major problem is faced when the user is not empowered enough to take decisions. In most of the case the business requirements are changed by the bosses of the business user. Such scenario are very common. another aspect is when is not aware about the impact of his requirement on other critical business process. In a ways when is user is rigid and closed focus

  Was this answer useful?  Yes

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.

 

Related Answered Questions

 

Related Open Questions