Live Webinar | Traditional Business Analysis vs. Agile Business Analysis

In a traditional Business Analysis environment, the business analyst has control of the requirements. Documentation of requirements in the form of user cases, functional specifications documents, business rules is done. Once the documentation is reviewed and signed off by it becomes the bible for the development team and any functionality which is not documented should be negotiated with the business user or will be deemed out of scope whereas in the Agile Business Analysis the requirements are documented as epics or user stories and the product owner has the flexibility to choose to remove any functionality or add new functionality. The change is discussed with the sprint team and they can choose to accept it as part of the ongoing sprint or in the next one depending on the criticality. We shall further discuss more on the differences on how the differences play a role depending on the organization structure and culture.
Agenda:
1. Requirements are documented in Use Cases, Business Requirements, Functional Requirements, UI Specifications, Business Rules vs Requirements are documented in Epics, User Stories and optionally Business (or Essential) Use cases.
2. Focuses on completeness of requirement vs focus on understanding the problem and being the domain expert
3. BA is representative of development team whereas in Agile BA is voice of the customer
4. Sign off vs Business needs\Value Add
5. Longer Turnaround vs Quick turnaround
6. Cost of Delivery vs Value Driven Delivery
7. How organization structure and culture play a role in deciding on waterfall or agile approach

Takeaway:
In this webinar you will get to know about the difference between Traditional and Agile Business Analysis.