Testable Requirements - How to Write Good Acceptance Criteria? ( acccri | 14 hours )

Basic knowledge of the IT product life cycle
Knowledge of nomenclature used in software development and IT project implementation.
Recommended experience in at least 1 IT project.

Level
2

Goals
Learn the importance of acceptance criteria for requirements quality and project risk reduction.
Acquire skills in creating requirements acceptance criteria and verifying them.

Advantages
Training provided by an expert with several years of experience in the IT industry and extensive knowledge of IT processes.
Emphasis on practice - necessary theory is supported by project practice, discussed topics are referred to real project situations.
Training delivered using tools used in requirements engineering, which provides an opportunity to learn the basic functionalities of such tools. 
Ability to apply the knowledge gained already during the training. 

Addressed to
System and business analysts, product owners, business owners.
Business representatives responsible for developing business needs.
Software and system engineers.
Testers, QA, people responsible for quality assurance of information systems and software.

Testable requirements are essential for ensuring that acceptance criteria are clear, measurable, and achievable.

This instructor-led, live training (online or onsite) is aimed at intermediate-level business and IT professionals who wish to learn how to write effective acceptance criteria for requirements.

By the end of this training, participants will be able to:

• Understand the importance of acceptance criteria.
• Create and verify requirements acceptance criteria.
• Apply different methods for describing acceptance criteria.
• Ensure the quality of analytical artifacts.

Format of the Course

• Interactive lecture and discussion.
• Lots of exercises and practice.
• Hands-on implementation in a live-lab environment.

Course Customization Options

• To request a customized training for this course, please contact us to arrange.

Introduction 

• Requirements and their quality.
• Acceptance criteria - what they are and what they serve.

Acceptance criteria - choice of approach

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

Acceptance criteria - methods of description

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

Acceptance criteria - quality control

• The role of testers / QA in ensuring the quality of analytical artifacts.
• The role of teamwork in quality assurance of analytical artifacts.
• Acceptance criteria vs. testing. 

Summary

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