Many organizations are starting to reap rewards from adding agile methods to their development practices. One of the roles most impacted by switching to an agile approach is the business analyst. Requirements are captured and documented differently on agile projects using novel techniques such as backlogs and user stories and by making extensive use of agile requirements modeling practices. Additionally, requirements are first captured at a broad, abstract level, prioritized using a 3-step approach, and then explored more deeply in cycles according to their priority.
LEARNING OBJECTIVES
Participants in this interactive session will learn:
- How user stories can be an effective technique for gathering user requirements.
- Tips & techniques on how to do user stories effectively.
- How much detail needs to be in a user story.
- How many user stories are required.
- How user stories emerge from use cases.
- How “themes” and “epics” play a role in requirements activities.
- How backlogs become central to the requirements management process.
- How to use agile modeling practices to improve requirements quality.
- And more…
TIMING
This course will be delivered over two half-day sessions (8:30am to Noon Eastern time) on November 6-7, 2025.
WHO SHOULD ATTEND
Business Analysts, Scrum Masters, Agile PMs, and Product Owners.
![Agile BA Basics [ONLINE]](https://img.evbuc.com/https%3A%2F%2Fcdn.evbuc.com%2Fimages%2F757839809%2F257950756571%2F1%2Foriginal.20240502-124622?w=940&auto=format%2Ccompress&q=75&sharp=10&rect=0%2C9%2C300%2C150&s=599787192e63e1ee8eccb7a5881aa5fe)