Trainings

Event Storming: explore your business and processes

exploring complex business domains and designing software systems

More Details Here
writing BDD

Writing Behavior-Driven Development: Building Your Specification

a process that encourages collaboration among developers, quality assurance experts, and customer representatives in a software project.

More Details Here
Implementing BDD

Implementing Behavior-Driven Development: your executable specification

BDD involves writing executable specifications in a human-readable language, which serves as an "executable specification" for the software.

More Details Here

Event Storming

Description

Event Storming is a collaborative and visual workshop technique commonly used in agile and lean software development. Alberto Brandolini developed it to explore complex business domains and design software systems. The process involves categorizing and capturing domain events, representing significant occurrences or changes within the business domain.

Participants can identify potential business rules and software components needed to implement the desired system through this technique. Event Storming encourages active participation and fosters shared understanding among stakeholders, enabling teams to prioritize requirements quickly and identify opportunities for improvement.

Goal

  • - Understand the fields that Event storming can be used for.
  • - Learn how to build a shared language using event storming.

Target Audience

QA, Architect, Developers, Business Experts, Product Manager, Product Owner

Prerequisites

  • - Experience in software development.

Format

  • - 30% theory, 70% Workshops.

Duration

  • - 1 Day.
  • Event Storming
  • Workshop
  • Process Modeling
  • Discovery
  • Big Picture
  • Events
  • Collaboration
Book The Training

Writing BDD

Description

Behavior Driven Development (BDD) is an agile software development approach that promotes collaboration between developers, testers, and business stakeholders to ensure the software is developed based on the desired behavior.

BDD involves defining system behavior regarding expected outcomes using scenarios or user stories. Plain language improves communication, and automated tests verify that the system behavior matches the desired results. BDD aims to reduce the risk of misunderstandings during development.

Goal

  • - Understand the usage, benefits, and drawbacks of BDD.
  • - Learn how to construct BDD with workshops between developers, QA, and Business Experts.

Target Audience

QA, Architect, Developers, Business Experts, Product Manager, Product Owner

Prerequisites

  • - Experience in software development.

Format

  • - 30% theory, 70% Workshops.

Duration

  • - 1 Day.
  • Behavior-Driven Development (BDD)
  • Workshop
  • Scenario
  • Behavior Specifications
  • Acceptance Criteria
  • User Stories
  • Collaboration
Book The Training

Implementing BDD

Description

BDD uses executable specifications written in natural language and can be executed to verify the system’s behavior. Executable specifications are typically written in the “Given-When-Then” format, which specifies preconditions, actions taken and expected outcomes.

This approach facilitates communication and shared understanding among stakeholders, enabling automated testing and reducing the risk of bugs. BDD is a robust methodology for delivering software that meets business needs.

Goal

  • - Understand the tooling of implementing BDD specifications.
  • - Learn techniques such as TDD double loop, which is recommended for BDD.

Target Audience

QA, Architect, Developers

Prerequisites

  • - Experience in software development.
  • - How to write a BDD specification.

Format

  • - 30% theory, 70% Code.

Duration

  • - 1 Day.
  • Behavior-Driven Development (BDD)
  • Gherkin
  • Given-When-Then
  • Step Definitions
  • Test Automation
  • Feature
  • Collaboration
Book The Training