Agile Business Analysis

Agile Analysis in Practice is a highly interactive learning workshop that builds on existing software development skills and instills specific practices on how to more effectively work with business and software development teams throughout the lifecycle of an Agile project. This course will help participants understand how to gather, express and manage changing business and technical requirements in an agile environment.

Overview

Audience

Business Analysts, Systems Analysts, Technical Analysts, User Experience Professionals

Duration

3 days

Pre-requisite

Agile Fundamentals

Objectives
  • Understand the Agile Analyst role and its responsibilities to an agile team
  • Learn effective methods for requirements gathering and elaboration in an agile context
  • Obtain an understanding of how to author quality user stories and related artifacts throughout the various phases of an agile project
  • Understand the analysis process during development iterations
  • Appreciate the growing role of User Experience in agile analysis practices

Course Outline

Introduction
  • Introduction of trainers and participants
  • Hopes & Fears exercise
  • Learning objectives
  • Intended audience
  • Agile is/Agile is not illustration
  • Agile best practices review
Introduction to Agile Analysis
  • What are your goals as an analyst? Independent of agile.
  • What are some of your current pain points?
  • A discussion of choices that can be made based on the adoption of practices or not
  • Responsibilities & accountabilities of a BA on an agile project
  • Agile analysis lifecycle discussion: problem identification through iteration analysis
  • Agile artifacts created throughout the lifecycle and when
  • Agile In Basket exercise
Project vision & Business Objectives
  • Shared understanding
  • Defining the problem case
  • Project vision
  • Tying back to business objectives
  • Project sliders
  • How to represent high level scope
  • Identifying project challenges
  • Models and phases
Understanding the Business Domain
  • Story elicitation
  • User roles and goals
  • Process models
  • Personas
  • Scenarios and User journeys
  • Prototypes
Requirements (aka Stories)
  • Story, Iteration, Release
  • The parts of a story card
  • Story format
  • Role, Goal, Value concepts
  • INVEST principle
  • Story anti-patterns
  • Other story writing guidelines
  • Inception level acceptance criteria
  • Assumptions
  • Non-functional requirements
  • Themes, Epics, Stories
Estimation & Release Planning
  • Representing stories
  • Analyst role in estimation
  • Analysis risk factors – understanding Complexity, Completeness and Volatility
  • Methods to prioritize stories
  • How to plan BA capacity for a release
Iteration Level Analysis
  • Review of Inception level artifacts
  • Anatomy of an iteration
  • Analyst role during an iteration
  • Narratives or other elaboration artifacts
  • Iteration level acceptance criteria
  • Showcases
  • Showing progress
Analysis Challenges
  • Splitting stories
  • New stories
  • Avoiding story explosion
  • Managing story analysis
  • Last responsible moment
Advanced Topics
  • The role of user experience in agile analysis
  • Analysis in distributed projects