Contact Us

CPRE RE@Agile Primer

RE@ Agile is a new certificate by IREB (International Requirements Engineering Board). Requirements Engineers and Business Analysts are often at a loss when it comes to perform their RE and BA work in an informal and fast paced environment. This certification prepares you for taking on the challenge and make your project successful.

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

This two-day workshop provides the essential information needed for those in the business analyst and requirements engineers role to be successful on Agile projects. Participants will use Scrum processes to write and prioritize user stories and get the detail needed for the Team to plan and build user stories. The course will familiarize participants thoroughly with Agile methodology in RE and BA and equip them for Agile software development.

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 methodology, 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 MoSCoW 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


  • Motivation to use Agile   
  • Mindsets and Values in RE and Agile   
  • Bridging RE and Agile Principles towards RE@ Agile   
  • Benefits, Misconceptions and Pitfalls for the Use of RE@ Agile   
  • Benefits of RE@ Agile
  • Misconceptions of RE@ Agile
  • Pitfalls of RE@ Agile
  • RE@ Agile and Conceptual Work    


  • Agile Methods (An overview)   
  • Scrum (plus good practices) as an Example   
  • Differences and Commonalities between Requirements Engineers and Product Owners  
  • Requirements Engineering as Continuous Process   
  • Value-driven development   
  • Simplicity as Essential Concept   
  • Inspect and Adapt   


  • Artifacts in RE@ Agile   
  • Specification Documents vs. Product Backlog
  • Vision and Goals
  • Context Model
  • Requirements
  • Granularity of Requirements
  • Graphical Models and Textual Descriptions
  • Definition of Terms, Glossaries, and Information Models
  • Quality Requirements and Constraints
  • Acceptance Criteria and Fit Criteria
  • Definitions of Ready and Done
  • Prototype vs. Increments
  • Summary of Artifacts
  • Techniques in RE@ Agile   
  • Requirements Elicitation
  • Requirements Documentation
  • Requirements Validation and Negotiation
  • Requirements Management  


  • Influence of Organizations on RE@ Agile 
  • Agile development in a non-Agile environment   
  • Interaction with stakeholders outside the IT organization
  • Product vs. project organization
  • The role of management in an Agile context
  • Handling of complex problems by scaling   
  • Motivation for scaling
  • Approaches for organizing teams
  • Approaches for organizing communication
  • Example Frameworks for scaling RE@ Agile
  • Impacts of Scaling on RE@ Agile
  • Balancing upfront and continuous Requirements Engineering in the context of scaling   
  • Initial Requirements Definition
  • Level of Detail for Backlog Items
  • Validity of Backlog items
  • Feedback and Update of the Backlog
  • Timing of the Development Cycle 
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