The Business Analyst in an Agile Environment



In this course, you'll learn how to discover your role within an Agile team's software development, how to adapt the techniques you already use to the Agile environment, and how to use some new requirement techniques specific to Agile. Each project will be different, and the role of the BA (business analyst) may vary from project to project. However, the concepts remain relatively stable and, assuming a willingness to be adaptable (agile), you will find an exciting new way of being a BA.

A major thrust of the course is the necessity of collaborative teamwork—others may take on part of the activities for which you have sole responsibilities in the Waterfall projects; you will be more closely involved in the work management of the team.

This course is consistent with the themes of the Agile Manifesto and the Agile Extension to the BABOK� Guide. Since most teams use hybrid approaches, the course considers Agile methodologies generically, rather than adhering to branded approaches, such as Scrum, XP, or Kanban.


BAs who are, will be, or plan to be part of Agile development teams


  • Knowledge and experience in business analysis in standard waterfall projects
  • General knowledge of Agile principles
  • **Pre-Course Reading required and available upon course enrollment**

Learning Objectives

  • The different versions of Agile and how they are usually implemented
  • The need for true teamwork and your work as a BA
  • How to help your team with soft skills
  • Agile requirements formats, user stories, epics, and themes
  • How to develop requirements at the last responsible moment using Real Options
  • How to use success indicators rather than success criteria
  • Agile requirement techniques
  • User stories with acceptance tests
    • Lightweight documentation
    • Collaborative gaming
    • Information radiation
  • Backlog management
    • Refining
    • Ordering
    • MoSCoW and Kano techniques for benefit estimation
    • Timing and story points for effort estimation
  • Your involvement in reviews and retrospectives
  • Your involvement in success indicator tracking

1. Critical Issues

  • Why Agile?
  • Being a Team Member
  • BA Skills
  • Increment Zero and BA Work
  • Real Options

2. Developing Requirements

  • Lightweight Documentation
  • Requirements Documentation
  • Epics and Themes
  • Developing User Stories
  • Acceptance Tests

3. Managing the Backlog

  • What is Backlog Management?
  • Refining the Backlog
  • When Is Software Done?
  • Reviews and Retrospectives
  • Before the Release
  • Success Indicators

4. Case Study and Exercises

  • Use Collaborative Games
  • Make Requirements Decisions in Increment Zero
  • Write User Stories
  • Groom and Order a Backlog