Agile Business Analysis
Agile Business Analysis
A 2-day course designed for business analysts and others that deal with requirements. The course is based on the IIBA™ Business Analysis Body of Knowledge® (BABOK®). Using the generally accepted practices from the BABOK the course shows how each can be used in agile ways. At the conclusion of the course participants know how to do agile business analysis as well as how use of those techniques can also help in non-agile environments.
Level:
Basic to intermediate
Length:
2 days
Intended Audience:
This course is designed for business analysts or anyone else that needs to deal with project requirements including project managers, product managers, product owners and others.
Pre-requisites:
None, but general reading about agile processes may be helpful.
Learning objectives:
- The principles that drive a successful agile process
- Agile process and roles
- Differences between traditional SDLC and agile
- Basic understanding of several Business Analysis Body of Knowledge® generally accepted practices
- Understand how to use generally accepted business analysis practices in an agile way regardless of process
Description:
This Power Agile™ course is designed to give a deep understanding of the difference between traditional requirements analysis and agile analysis. Terminology is defined and explained. Generally accepted practices defined in the BABOK are explained and utilized during class exercises. Participants are encouraged to use the agile techniques regardless of their development methodology.
The course also dives into the myths surrounding agile processes and the myths about business analysis. The myths are debunked using a very straightforward and logic driven approach. The result is a deeper understanding of both agile and business analysis.
A single sample project is used during the entire course. This allows participants to see the process and analysis in context. Learning by doing gives participants to gain deep understanding, but also gives an opportunity to ask the hard questions that may arise. Using the safe environment of a sample project allows everyone to experiment and learn rather than fear failure or rejection.