YUNOVA · Business Analysis
Module 9: Agile business analysis
Business analyst role in Scrum
Key points
- In Scrum a BA often supports the Product Owner with requirements.
- The BA helps refine the backlog and write clear user stories.
- Acceptance criteria from the BA guide the team's testing.
User story mapping
Key points
- A story map lays user activities left to right in the order users do them.
- Stories sit under each activity, ranked from most to least important.
- Horizontal slices across the map define releases.
MoSCoW prioritisation
Key points
- MoSCoW sorts requirements into Must, Should, Could and Won't have.
- Must-haves are needed for the release to be usable at all.
- Won't-have items are agreed as out of scope for now.
Requirements in agile versus waterfall
Key points
- Waterfall captures detailed requirements up front in a signed document.
- Agile refines requirements continuously as user stories in a backlog.
- Each approach changes how the BA handles change requests.