megrath

 Profile Answers by megrath 

• Sep 30th, 2008

 

If the business users ask for a particualr requirement to be included in the current one when the project is near completetion, i would have them look at the requirement document and show them the requirements that they wanted..this is the reason i always prioritize the users requirements against the manager's priorties..I would do an impact analysis and show the follwing results to the PM and the business users  and ask the PM to make a decision:

1. Whether this change is causing project delays, cost overruns and extra manpower
2. Does it benefit the organisation.
3. If we can include the change in the next release.

nareshious

 Profile Answers by nareshious 

• Sep 26th, 2010

 

It is essential to know why this change propped up now, It is also essential to check if it is a regulatory requirement. It is essential to work on it to find out, how this change would impact the current project plan. If this could be taken up later, would it be easy to to incorporate this in the existing development. How much would it cost. Based on the answers to these question a decision has to be taken with the business users. 

sureshvegi

 Profile Answers by sureshvegi 

• Jul 23rd, 2012

 

for BA it is always a tough job when it comes to change s in requirements when the project is in ongoing process,but as a BA we have to do it ,analyze those proposed requirements and find if any impact is they on related tasks,so on after that we will inform the client about it if we have to change requirements then automatically budget and schedule will increase if the client agrees for that we will proceed by discussing with my project manager.

Shivaji Adhikary

• Mar 10th, 2015

 

Changes might come as UAT Feedback. Depending on the new business scenario explored to manage the change, both the BA and the client have to come on a common page of understanding.

Manju

• Aug 20th, 2015

 

Its a difficult task, because a new requirement may effect the existing flow. So business analyst should analyse the requirement well. And should analyse the complete flow of new requirement over the existing one. And while explain these changes to the developers, business analyst should be confirm that he/she didnt miss any point.

Rudy Khatiwada

• Aug 26th, 2015

 

In the context of change requirement, If we are at point where requirement gap has been already identified and if requirement change request has come with through appropriate ad proper channel to fill the gap and the current SDLC methodologies has capabilities to accept the changes then we only we can take first initiation. But As a Business Analyst we should be capable enough to interpret how important it is and how is this literally necessary to make changes to bridge the gap and we should be able to make sure that new requirement will not affect the existing flow rather it will make complete flow to achieve what we expected. we should be able to visualize in term of As Is and To Be with details.

Abhishek Gupta

• Oct 9th, 2015

 

Change must analyze first, with targeting where to change and how to change. That change test cases must be prepare for proper testing. Existing bug or gap must analyze at high level risk and that change implication must analyze first.

Achintya Jain

• Oct 10th, 2015

 

We need to analyse how big or small is the requirement and the most important is to do impact analysis. For example, if there could be a dollar impact then we need to apply the changes with some flag so that previous deals are not impacted or if its only a display change then the system should have capabilities to easily adopt that change.