Rutuja Mishra Latest answer
Answered on Nov 19, 2019
Agile keeping teams away from the traditional beliefs of writing lengthy requirements and contract documentation. If there is not much requirement writing, then why business analysis in Agile.
The key success of any project, whether it's Agile or not is to meet the need of the hour. Business analysis collects various diversification to structure and put them on one table. Agile is about learning and adapt as you move forward. Agile creates value for customers by delivering a working piece of software in the shortest period. In other words, Agile delivers the work in an iterative manner.
Although it’s not true, you can look at every iteration in agile as the traditional method of delivering software. Any person in the agile team can take the role of an analyst. He/she is the person always talking to the business about the product roadmap and exploring the product need on a regular basis. Every iteration needs requirement elicitation, prioritization, elaboration, test and validation. A business analyst in an Agile project is primarily involved in:
Working with the business team to align requirement towards the project goal
- Feature classification
- User story writing
- Acceptance criteria
- Validation of completed work
- Collect user feedback
- Adjust change in requirements
- Domain trainer
- Agile coach
