On requirements changes questions @ 16:00 , yes with Agile, since it is incremental /iterative project methodology , we don't need to use RTM here as we can embed the changes in Product Increments (or if changes are risen during testing , it can become a defect and sneak into Product backlog ) which after approval (as you rightly said by the PO/SH) can be part of future sprints.
So if the change request comes during development phase, i understand the requirements of the BA, but if your development team is not coordinating.. is there any role of a BA or it is PM who now has to tackle. And if the release is near and it timeline is critical, how does a BA go about. Do they take some work out from development team in order to prioritize change or not accept the change in the first place no matter how critical it is. How to resolve this conflict, and would love to know if something like this has ever happened in your career and how did you tackle it.
The key to all of your questions is team communication. Regardless of when issues are found, the project team has be well informed to make the right decisions. Dev Team --> BA/PM. BA/PM --> Stakeholders. Stakeholders will make the final decision based on feedback/recommendations from the project team.
If you are working in the Waterfall environment, it will require a Change Request. If you are in the Agile environment, design/functionality features can be added to the backlog.
![BOWKYLION - วิงวอน (ex-change) [Official MV]](http://i.ytimg.com/vi/cLdnZWDaO-w/mqdefault.jpg)
On requirements changes questions @ 16:00 , yes with Agile, since it is incremental /iterative project methodology , we don't need to use RTM here as we can embed the changes in Product Increments (or if changes are risen during testing , it can become a defect and sneak into Product backlog ) which after approval (as you rightly said by the PO/SH) can be part of future sprints.
Thank you for the feedback!
So if the change request comes during development phase, i understand the requirements of the BA, but if your development team is not coordinating.. is there any role of a BA or it is PM who now has to tackle. And if the release is near and it timeline is critical, how does a BA go about. Do they take some work out from development team in order to prioritize change or not accept the change in the first place no matter how critical it is. How to resolve this conflict, and would love to know if something like this has ever happened in your career and how did you tackle it.
The key to all of your questions is team communication. Regardless of when issues are found, the project team has be well informed to make the right decisions. Dev Team --> BA/PM. BA/PM --> Stakeholders. Stakeholders will make the final decision based on feedback/recommendations from the project team.
What if the scope changes and the project has already started and in its Design phase. . . what is the role of BA here.
If you are working in the Waterfall environment, it will require a Change Request. If you are in the Agile environment, design/functionality features can be added to the backlog.