Agile Business Analysis

Bascom Bridge’s  Agile Business Analysis training teaches attendees how to serve as analysts on Agile projects.

AGILE TRAINING OBJECTIVES

• Identify the key practices of Agile analysis and ways to make requirements practices ‘lean’
• Understand the value of a product roadmap and release planning for large, complex products
• Describe how Agile methods differ from traditional development
• Define the key principles, practices, and processes of Agile development
• Identify the roles people play in an Agile project
• Define and analyze Agile requirements

AGILE TRAINING PREREQUISITES

It is recommended that participants have experience working on Agile teams or have prior Agile training. However, we would be delighted to tailor it to any level of prior experience.

AGILE TRAINING MATERIALS

All attendees receive comprehensive courseware.

SOFTWARE NEEDED FOR EACH PC:

No software is required. Students should be seated in pods of 3 or 4, with a notebook and pen for each student. Each pod should have a flipchart with multiple colors of markers. The instructor will require connectivity for her/his laptop to a projection system and Internet.

AGILE TRAINING OUTLINE

• Introduction to Agile Development
  • Agile Overview
  • The Agile Potential
  • The Agile Manifesto
  • Agile Alone is NOT Enough
  • Can Agile fail?
  • THE Best Agile
  • Self-Organized Teams
  • The Business Analyst Role In Agile
• Business Analysis in Agile Projects
  • Multiple Levels of Planning
  • The “Ever Unfolding Story”
  • Progressive Requirements Elaboration
  • How to do Requirements Driven Agile
  • Requirements as the Basis for Agile Backlog
  • How Agile Methods Impact Requirements Risks
• Agile Business Analysis: Product View
  • Agile’s Big View
  • Working with Your Product Owner
  • Product Vision
  • Product Roadmapping
  • Keeping Your Eye on Requirements
• Agile Business Analysis: Release Planning
  • Release planning
  • User stories, epics, and sagas
  • Quality attributes and interfaces
  • Grooming the backlog
• Agile Business Analysis: Sprints and Iterations
  • Use Cases in Agile
  • Actors and Roles
  • Understanding User Stories
  • Comparing and Contrasting User Stories and Use Cases
  • Right Sizing User Stories (just enough detail and no more)
  • Defining Done
  • Testing Stories
  • Estimating in Agile Projects
  • Calculating Capacity
  • Determining Velocity
  • Selecting Stories
• Metrics To Remember
  • Velocity
  • Software Quality
  • Team Success and Sustainable Pace
  • Metrics Overview
• Conclusion