BA should aware the change request in any point of the time. A change request (CR) is basically any change in the initial set of signed off requirements.Change request differs in number and complexcity across the business projects and may come in before,during or after the implementation of a solution. Hence it is a sensitive for the project even in agile method there is a flexibility in the implementation of the project and vendors should ensure the high level set of requirements are discussed and agreed upon.
For example lets think project is initiated and progressing through time and all of sudden and the client has come up with some new requirements. These change request may affect your current project and its timeline.
To start this change request BA has to draft the specification document and sit with clients and understand the reason for the rew requirements. When he sits meeting with the client he/she should analyze and clarifies exactly what the request is asking you to do and how to improvise this change request to communicate with the development team and testing team.
Once the BA analyse the change he/she need to discuss about the reason for the change,impact of the change,feasability study,effort required to implement the change, change request follows the predetermined approval process with the team and organization.
Some Key point to keep in mind for BA:
1.Keep the specification document ready.Know and revise the changes being debated and prepare your points.
2.Discuss the approach of handling change request with your manager/senior management.Some vendor wants to more flexible if the client is too important. Some don’t want to take risk dueto to lack of bandwidth.
3.If the change is really small and cosmetic,business analyst tend to accept them inorder to maintain good rapport with the clients. Always check fesability study with development team hence what is small to you sometimes it will be bigger work for them.