Performing business analysis on a Scrum team can seem overwhelming given the level of agility provided to product owners. It doesn’t have to be overwhelming if you’re armed with the right information and solid techniques. After a brief overview of agile project delivery, this class will teach participants how to elicit requirements in agile projects. Agile metrics and product centricity are also reviewed, including how to work with the product owner to develop a product roadmap, and a discussion of best-practice techniques for eliciting requirements will take pace.

Audience: This workshop is intended for business analysts or those performing business analysis tasks. It is also suitable for anyone wanting to learn Agile/Scrum analysis in-depth, including any stakeholder or participant in an organization planning to apply Agile.
Course Duration: 2 days
Prerequisites:

Prior experience with business analysis on projects is helpful but not required.

Course Objectives:
  • Describe agile values and principles, emphasizing the importance of business analysis work on an Agile project
  • 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 methods
  • Define the key principles, practices and processes of agile development
  • Identify the roles people play in an agile project
  • Define and analyze agile requirements
Course 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)
    • 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