How did you make sure that the requirements you gathered from the users are exactly what they are looking for.docx

8/17/2019 How did you make sure that the requirements you gathered from the users are exactly what they are looking for…

1/3

1) How did you make sure that the requirements you gathered from the users are exactly what

they are looking for?

After every requirement gathering session, I developed meeting minutes that was a preliminary

draft of the requirements gathered. These minutes were sent to the business users that were

involved for review and to check for any disconnects and additional information. After theapproval from all concerned parties was received the final document was produced and put into a

formal template format for sign-off from the business users.

2 At the end of the project, was there any case when the user might have come up and said

this is not what desired from the system? !In other words, they e"pected more from the

system. #ow did you handle that$ %id you enhance the requirements and re-released the

product$

I was in such situation during my most recent pro&ect. The users e"pected a functionality which

was not considered as part of the first release and they thought that the requirement e"isted in the

functional requirements document. I pulled up the requirement specification document, the

meeting minutes and showed them that the functionality had never been requested for. 'ince this

was not an immediate requirement, the business users agreed to wait for the ne"t release of the

application to incorporate the functionality.

( #ave you worked on any )ational tools$

I have normally worked on )*+ methodology and )ational tools are based on the same. I am

quite well versed with )ational )ose for making use case diagrams, use case documents,

realiations etc. I have used )equisite pro for managing and documenting the requirements. #ow far were you involved in the testing phase$

These would be specific to your resume based on what pro&ect is being talked about.

"ample/

%uring the testing phase I was responsible for/

%eveloping Test 0ases and Test +lans.

)ecording the observations of the users and reporting them back to my manager.

%iscussing any changes and updates with the user and if need arises handling the 0hange)equest procedures and tracking.

1 #ow do you decide which features to include in what releases$

veryone wants there features to be release in the st iteration. 3e normally decide on the

features of the st release or any releases ahead on the basis of/

• 4usiness priority

• 3hat feature goes st based on the scope document.

• )eview with the business managers what they require in the st release and get their

approval.

• 4usiness comple"ity5)isk

6 3hat is your main strength or what do you think that you have accomplished in your last pro&ect

with which you are most proud of$

I think my strength is my ability to be detail oriented. There are always times when there aredisconnects or constant changes in the pro&ect and if information and documents are not well

organied, it might lead to a disaster and failure.

I am also quite detailed oriented which helps me to list the use cases and requirements properly

and comprehensively so that there is minimum element of doubt.


2/3

7 3hat were the risks involved in the pro&ect$ #ow did you come with the solutions for those

risks$

There were several risks involved in the pro&ect/

'ecurities )egulations/ %uring this pro&ect there were a lot of regulations involved which needed

to be considered while developing the site. 8or e"ample/ who should be given what kind of

access to the system, what path will the document How do you deal with difficult

stakeholders?'takeholders sometimes could be difficult to deal with but we could overcome this

situation by/+atiently listening to them and being polite. 9ake them understand the situation from

a prospective they understand.

'how a commitment to working with them.

9ake them realie how their interests will be realied when they are more open andcollaborative.

ngage them and make them realie that their contribution is valued.

!hat is the mportance of a "low #hart$

The flow charts gives a clear graphical representation of an implemented process,This makes the system simple to understand for all persons involved in the pro&ect.

"plain briefly the use case 9odel$

The use case model requires a use case diagram, It describes the business environment,It:s primary goal is to show the series of events and actions with in any given process that

will be performed by an actor

3hat is *9; 9odeling$*9; means unified 9odeling ;anugae,Its is industry standard language for

constructing,visulaing and documenting the different componenets within the system.

$ame the skills which %usiness Analyst should have?

continuous learner, Analytical skills, problem solving approach,

thinking beyond the bo", tech savvy !can keep updating what are the latest technologies released

in market and how those are important. Team or people management, solid communication,

documenting skills !written nglish, team player, devising new solutions, market research etc !if

know some more you can add

!hat do you think a&out challenges faced &y %usiness Analyst?

0hange management is the biggest challenge because this happens in real time as well. After

requirements stage when development is started client will come-up some changes or

enhancements. 0ross departmental or cross team management ? like conflict management

between teams. Also individuals. This requires soft skills and smartness. 0ommunication problems ? In real time this can happen. @ou might be good in speaking and understanding the

nglish language. 4*T sometimes it happens like %ifferent people across the globe speak

different style of nglish. In *'A itself 9e"ico people speak nglish differently. )omans speak

different nglish. 'o at initial level to understand the accent can be a challenge but after some

time you will become perfect

!hat is your understanding on ' (isk and ssue?


3/3

)isk is something which can be forecasted and can be handled by formulating mitigation plans.

)isk which happened is called Issue. There will be contingency management or issue

management to solve issue. 4asically we will be not solving the issue but will try making

%amage control and take it as learning for other pro&ects.

3hat would you do if you havent received all the required signoffs on phase documentation

submitted for approval$ #ighlight risk management process - how to flag these$ )esolution - ofsuch scenarios, by working alongside +9

"plain how you organie or prioritie your workload

9ake a list. 3ork out what order to do things in by thinking about which tasks are urgent

and how important each task is. If not sure what:s urgent and what isn:t, or howimportant different tasks
http://www.geekinterview.com/question_details/88996http://www.geekinterview.com/question_details/88996

Documents

How did you make sure that the requirements you gathered from the users are exactly what they are looking for.docx