Build skills defining small, valuable, well-defined product requirements for delivery. You learn how to create a shared understanding of product needs using collaborative techniques and slice them into well-understood, valuable chunks for development. This training focuses on iteration or work-in-progress (“Now-View”) within the context of the overall product (“Big-View”) and product releases (“Pre-View”). Through practical, integrated exercises, you learn to elicit, evaluate, and explore product backlog items, adapt analysis practices, and define product needs.

You experience how to slice minimum marketable features (MMFs) into right-sized stories, how to build user story maps, and practical techniques for making stories “ready” for iteration planning and team delivery. You learn to utilize option analysis and story slicing strategies, with a keen focus on business value.  This training emphasizes defining and continual pruning a healthy product backlog, how to collaborate to develop agile requirements, and the power of “doneness”. 

You gain an appreciation of both the content and the timing of requirements analysis in agile projects, and learn why it’s crucial to collaborate with the entire project community throughout each delivery cycle. 

You leverage EBG’s Agile Analysis Roadmap to learn when, where, and how to draw on analysis models. Understand how to calibrate the content, format, and timing of requirements analysis to prepare for and participate in planning (iteration or work-in progress; release and product roadmap) as well as the daily analysis needed to transform requirements into tests and code.

If you choose EBG's popular "Agile Jump-Start" package, the team will participate in the Agile Business Analysis training and then will start applying the principles on their own agile project while being mentored by an EBG expert.

• Understand the agile framework
  o    Identify how agile differs from traditional development 
  o    Define key practices of agile development
• Analyze, slice and elaborate backlog items
  o    Identify minimum marketable features (MMFs)
  o    Write user stories
  o    Model users with roles or personas
  o    Build a user story map
  o    Analyze and prioritize options to identify “right size” user stories
  o    Identify and specify nonfunctional requirements
  o    Understand ways to assign business value to requirements 
  o    Add elements to requirements to increase their business value
• Validate requirements
  o    Define doneness criteria
  o    Calibrate documentation practices for your project  
  o    Write scenarios and acceptance tests
  o    Describe the value of supplementing user stories with organic analysis models
• Describe multiple ways to prioritize requirements 
• Estimate agile requirements
• Explore product and release planning activities 
• Appreciate the business value of just-in-time, just enough agile analysis  
• Understand how requirements are the basis for agile planning

• Agile in a nutshell
• The product backlog
• Doing agile 
• Agile roles
• Key practices
• Scrum in a nutshell

2. Intro to Agile Requirements

• Traditional vs. agile requirements 
• Requirements-driven agile planning
• Requirements the agile way 
• Agile Analysis Roadmap

3. Slicing Requirements for Value

• Criteria for Ready Requirements
• Slice requirements for value
• Minimum marketable features (MMFs)
• Now-View 
• User stories, User story map 
• Slicing strategies
• Quality attributes
  
• Acceptance criteria (doneness)
• User acceptance tests and scenarios 
• Design and implementation constraints
• Cross-cutting requirements  
• Pruning the backlog
• Threading Now-View requirements
  

4. Agile Estimating and Prioritizing

• Now-View planning agenda
• Estimating in agile
• Defining business value
• Prioritizing requirements
• Estimating in agile

5. Analysis Across Product Views

• Big-View 
• Pre-View 
• Organic modeling
• Agile documentation
  

• Multiple levels of agile planning
• Roadmapping
• Release planning
• Iteration and WIP planning
  
• Work ahead analysis
• Agile requirements wrap up

7. Adapting and Adopting Agile Product Delivery Practices

• Adopting and adapting to agile
• Change is a process
  
• Agile community practices
• Agile delivery practices
• Agile planning practices
• Agile tuning and improving

Customize Your Agenda Based on Participants’  Background and Needs:

• EBG works with you to decide which of a variety of exercises and simulations—all based on a integrated case study—to use in the training
• Add advanced topics (an additional day or replacing basic content). These include:
• Agile Dependency Analysis
• Agile Business Rules