Contact Us

Business Analysis for Agile Practitioners

You will apply what you learn in a series of hands-on activities using a realistic case study that takes you through the agile requirements process, with example solutions. This course can also be taught on-site for a project team. 

Duration: Classroom - 2 Days | Virtual - 4 Days
Why Take This Course:

Today, more organisations are adopting Agile development and the trend is expected to continue. Agile development streamlines process overhead and improves predictability through better risk management.

Some popular Agile flavours today include Scrum and XP. Although these flavours describe in details the steps in Agile development, they do not elaborate on how to manage the requirements. This Business Analysis for Agile Practitioners course has been designed to introduce participants to the entire Agile development process, with a focus on requirements. 

Through this two days course, participants will also be equipped with knowledge and skills to effectively perform business analysis in Agile projects. Participants will learn how to write and validate user stories. They will also be engaged in hands-on sessions to help facilitate and enhance the learning process.

You will apply what you learn in a series of hands-on activities using a realistic case study that takes you through the agile requirements process, with example solutions. This course can also be taught on-site for a project team. The team’s project can be used as the basis for the course activities, resulting in the creation of key artefacts, such as the Product Backlog, the selection and prioritization of themes and stories for releases and iterations, and release and iteration plans.

Learn How To:

The course will help you practically learn on the following areas:

  • Describe agile values and principles, emphasizing the importance of business analysis work on an Agile project.
  • Describe the Business Analyst role on Agile projects
  • Key principles of performing Business Analysis activities on Agile projects
  • Explain Scrum roles and responsibilities, focusing on the role of the business analyst
  • Define Agile requirements with user stories to build a product backlog
  • Describe relative value and use techniques to prioritize user stories
  • Release planning:
    • Discuss the important role the business analyst plays in release planning.
    • Describe the steps in release planning
    • Create a release plan
  • Groom the product backlog:
    • Understand the importance of elicitation and requirements analysis in getting the detail necessary to build the product increment
    • Use just enough requirements modeling to groom the product backlog
  • Explain the importance of Scrum ceremonies and artifacts
  • Describe the importance of and steps in a Scrum retrospective
  • Participate in a class retrospective
Contents:

Quick Review of Agile Basics

  • Agile principles
  • Scrum terminology
  • Scrum roles and responsibilities
  • The BA role on Agile projects
  • The Team environment
  • Defining the product vision
  • Agile Requirements

The Agile/Scrum requirements process

  • User roles and personas
  • Components of a user story
  • Guidelines for good user stories
  • Non-functional requirements, business rules, and other constraints
  • Workshop: write user stories and create product backlog

Release Planning

  • Steps in release planning
  • Theme prioritization techniques
  • User story mapping
  • MoSCoW prioritization technique
  • Workshop: prioritizing user stories
  • Workshop: map user stories

Grooming the Product Backlog

  • Defining the product boundaries
  • Elicitation techniques to clarify user stories
  • Modeling to obtain the detail
  • Data, process, and interaction requirements
  • How prototypes help visualize the product
  • Acceptance test criteria

Sprint Planning

  • Levels of planning in agile
  • The BA role in sprint planning
  • Sprint plan
  • Selecting user stories for Sprint plan
  • Decomposing stories into tasks
  • Overview of process to estimate tasks
  • The sprint goal, plan, and commitment
  • Workshop: create sprint plan

Ceremonies and Artifacts

  • Events during a sprint
  • Activity: participate in a daily scrum
  • Incorporating feedback/handling changes to the product backlog
  • Quick look at other sprint activities (testing/building)
  • Importance of retrospectives
  • Workshop: class retrospective
Format: To help assimilate the tools and techniques learned, there is a mixture of group and team exercises throughout the course. The use
of a realistic case study will help reinforce concepts learned. Be prepared for a high level of participation. Each participant will receive a comprehensive student guide complete with examples and workshop solutions.
Who Should Attend: This course is valuable for all agile team members: Business analysts, product owners, customer, users, scrum masters or project coaches, testers, developers and architects – anyone on a project who is involved in eliciting, defining, analyzing, and validating business needs and requirements in order to transform them into working software.
Prerequisites: None

Learn More About Our Association