Agile Business Analysis, 3-day Workshop, Boston-MA, USA

Burlington, Massachusetts
Wednesday, July 13, 2011
Agile Business Analysis, 3-day Workshop, Boston-MA, USA
Wednesday, July 13, 2011 9:00 AM -
Friday, July 15, 2011 5:00 PM (Eastern Time)

Knowledge Services
10 Burlington Mall Road
Ste 225
Burlington, Massachusetts 01803
United States

Map and Directions

<< Back to All Workshops

  workshop abstract-Analysis in Practice-3 day.pdf


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.

  • Business Analysts
  • Systems Analysts
  • Technical Analysts
  • User Experience Professionals
Duration: 3 days

Agile Fundamentals

Learning 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


Day 1:  9:00am - 5:00pm
  •  Morning
    • Opening
    • Introduction to Agile Analysis
    • Exercise: Agile In Basket
    • Project Vision & Business Objectives part 1
  • Lunch Break
  • Afternoon 
    • Exercise: Product Box
    • Project Vision & Business Objectives part 2
    • Facilitation Patterns Workshop
    • Retrospective
Day 2:  9:00am - 5:00pm
  •  Morning
    • Understanding the Business Domain
    • Exercise: Roles
    • Exercise: Personas
    • Exercise: Prototyping
  • Lunch Break
  • Afternoon
    • Requirements aka Stories
    • Exercise: INVEST Exercise
    • Exercise: Story Mapping Exercise
    • Retrospective

Day 3:  9:00am - 5:00pm
    •  Morning
      • Estimation & Release Planning
      • Exercise: Analysis Risk Factors
      • Exercise: Span Planning
      • Iteration Level Analysis
      • Exercise: Create Narrative Template
    • Lunch Break
    • Afternoon 
    • Analysis Challenges
    • Advanced Topics
    • Parking lot, wrap up, retrospective

Topics Covered

• 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
o Problem identification through Iteration analysis
• Agile artifacts created throughout the lifecycle and when
• Agile In Basket exercise
Project vision & Business Objectives
• How a common understanding at all phases reduces errors and provides efficiency
• Defining the problem case
o Cause & Effect diagram
• Project vision
o Elevator pitch and other techniques
• A visual on how everything ties back to business objectives
• Project sliders - a tool for prioritization and planning
• How to represent high level scope
• How to identify potential project challenges
• A discussion of models and phases
Understanding the Business Domain
• Techniques that help elicit stories and the artifacts that are produced
• In general, these concepts are common to traditional and agile methodologies. It is the way they are gathered and represented that differs
• Defining the Roles of users and their goals for the system
• Representing the 'as is', pain points and 'to be' process models
• Defining Personae - Roles could have multiple personae
• Using scenarios to understand how personae work through the system
• Creating low-fi or mid-fi prototypes to demonstrate the system using a low cost approach
Requirements (aka Stories)
• Representation of the concepts of story, iteration, release
• The parts of a story card
• As a, I want to, so that…
• Role, Goal, Value concepts
• Review of each of the INVEST principles
• INVEST principle exercise
• Looking at anti-patterns and discussing how to make them better
• Other story writing guidelines
• A look at inception level acceptance criteria
• Why assumptions are important when initially writing stories
• Ways to represent non functional requirements - stories, notes tree
• A look at Themes, Epics and how they are broken down into stories.
Estimation & Release Planning
• Discussion of how to represent stories - Master story list, story map, story boarding
• Analyst role in estimation
• Analysis risk factors - understanding Complexity, Completeness and Volatility
• Methods to prioritize stories - relative prioritization, usage based, games
• How to plan BA capacity for a release
Iteration Level Analysis
• A review of the artifacts produced during inception and what is to come
• Anatomy of an iteration
• Discussion about how the analyst is working on stories from 3 different iterations at one time
• A proposed process for creating narratives
• Narrative details - template, why narratives, how do they benefit various roles
• Iteration level acceptance criteria - examples, why the different level of detail, who writes them
• Showcases - why do them, who attends, what is the outcome
• Other methods of showing progress or status of stories
Analysis Challenges
• Techniques for splitting stories into smaller stories
• How to handle the new stories
• How to avoid story explosion
o One story turns into many
o Scope creep or missed requirements
• Managing story analysis
• Introducing the concept of the Last Responsible Moment and how to handle it
Advanced Topics
• The role of user experience in agile analysis
o Contextual inquiry
o Interaction design
o Prototyping
• Analysis in distributed projects
o Communication and strategies for supporting developers and QA 


Contact Information

Payment Instructions

  • Registration Fee: $2,250* per person

    * All registrations are final and cannot be canceled.
    * Payment by Visa, Mastercard and American Express accepted

    Upcoming Workshops

     View Workshops Calendar

© 2017
Quick, easy and affordable online event registration and event management software for all event sizes.