George Estregan

• Feb 19th, 2007

 

The availability of the people (e.g. managers, supervisors and the end users) the BA wants to talk with for gathering business requirements.  These people have regular daily works to do and their time to spend in the gathering sometimes hard to schedule and for this reason gathering business requirements is delay.

Noypi

 Profile Answers by Noypi 

• Feb 19th, 2007

 

The availability of the people (e.g. managers, supervisors and the end users) the BA wants to talk with for gathering business requirements.  These people have regular daily works to do and their time to spend in the gathering sometimes hard to schedule and for this reason gathering business requirements is delay. 

nehasahu

 Profile Answers by nehasahu Questions by nehasahu

• Jan 4th, 2009

 

I feel the main problem which a BA faces is changing requirements. In some project the requirements keep on changing.
The BA has to keep a track of all those requirements.

mhbhat

 Profile Answers by mhbhat 

• Jun 22nd, 2009

 

Problems BA can face while requirement gathering  

• Conflicting requirements/Controdictory Statements
• Undocumented Process
• Lack of access to the end-users
• Bad requirements
• Stakeholder's design of the solution
• Difference in industry knowledge
• Installability of UI
• Communication issues such as assumptions, glossery of terms, interprettation problems etc