One of the key contributions of a Business Analyst to a project is to elicit and communicate requirements. More often than not team members performing the Business Analysis function are bogged down by various requirements documentation methods like use cases, user stories, etc. and even more so by the various formats within each method. I want to share my experience of using these methods, especially in Agile environments, highlight the pros and cons, so the attendees can use the best method depending on the stakeholders.
Please find Dharmesh’s material here: Dharmesh.