One topic that I have not seen examined, is how using a different System Development Life Cycle (SDLC) methodology affects a Business Analyst's requirement gathering approach. There are many different methodologies that are used on projects. Some of the different SDLC models include:
For a waterfall model you will want to get all of your requirements before you move to the next stage of the development life cycle (let's exclude change requests from this discussion.) Whereas when you are working on a project using an Agile methodology, you are providing discrete requirement sets based on their priority.
As a Business Analyst you must be flexible in your approach to conform to the SDLC that your project will use. When an Agile model is being employed, you must be willing and able to filter out everything that does not focus on the specific requirement set that has been chosen. For individuals that are used to a waterfall approach, letting go can be a difficult mental hurdle to cross.