Get in Touch

Course Outline

Introduction

  • Requirements and their quality.
  • Acceptance criteria - definition and purpose.

Selecting an Approach for Acceptance Criteria

  • Analysis of the project context.
  • Identification of stakeholders and their expectations.
  • Acceptance criteria in relation to DoR and DoD.

Methods for Describing Acceptance Criteria

  • Scenarios.
  • EARS standard.
  • User stories and textual acceptance criteria.
  • User stories and Gherkin.

Quality Control for Acceptance Criteria

  • The role of testers/QA in ensuring the quality of analytical artifacts.
  • The importance of teamwork in quality assurance of analytical artifacts.
  • Distinction between acceptance criteria and testing.

Summary

  • Workshop summary.
  • Best practices and key elements of the information management process.

Requirements

Foundational knowledge of the IT product life cycle.
Understanding of nomenclature in software development and IT project implementation.
Recommended experience in at least one IT project.

Level
2

Goals
Comprehend the importance of acceptance criteria for requirements quality and reducing project risks.
Develop skills in creating and verifying requirements acceptance criteria.

Advantages
Instruction delivered by an expert with years of experience in the IT industry and deep knowledge of IT processes.
Focus on practical application - essential theory is reinforced by project practice, with discussed topics linked to real-world project scenarios.
Training utilizes tools commonly employed in requirements engineering, offering insight into their basic functionalities.
Opportunity to apply acquired knowledge immediately during the training.

Intended Audience
System and business analysts, product owners, business owners.
Business representatives responsible for defining business needs.
Software and system engineers.
Testers, QA professionals, and individuals responsible for quality assurance of information systems and software.

 14 Hours

Related Categories