Over the past decade, eXtreme Programming practices like User Stories, Test-Driven Development (TDD), Behaviour Driven Developer (BDD), Refactoring, Continuous Integration and Automation have fundamentally changed software development processes and inherently how engineers work.
BDD is practice for efficiently evolving useful code. While its name implies that it’s mostly about development, BDD is primarily about collaboration and delivering business value: it keeps programmers focused on exactly what they need to build and helps them avoid over-engineering.
This workshop offers a comprehensive, hands-on introduction to behaviour driven development via interactive discussions, multimedia content, hands-on exercises and quizzes. We’ll demonstrate the BDD Rhythm. Also explore the foundations of BDD with the help of various patterns, strategies and your programming language specific BDD tools & techniques. Participants will understand how BDD simplifies evolving lean, valuable, useful, fully specified software.
We’ll give a small live demo of BDD and then Participants will get their hands dirty by using these techniques on different problems using their language specific BDD tools. We’ll conclude by highlighting the key benefits, common challenges and different styles of BDD.

Learning Outcomes

Understand how the whole team collaborates around scenarios to support development

Learn to drive the development (design and implementation) of a User Story using BDD.

1 or 2 Days of Mentoring via Pair Programming with Developers on your code base

To get your team kick-started with the learning from the workshop, we recommend, that our trainer spends a day or two, working with your team on your code base.

Each day will be reserved for 4 pair programming sessions. During these sessions, the workshop participants will take specific examples from their projects, where they are finding it difficult to apply any of the practices learned in the workshop. The trainer will then pair with an individual to show how to resolve those challenges.

At the end of the day, the 4 volunteers will summarize their learning by showing before and after code from their respective pairing session to the rest of the group.

Pre-Post Programming Assessment

The goal of these programming assessments is to identify real and quantifiable measures for the learning achieved through our workshop.

Objective:

Get a quick understanding of your knowledge and skill level with respect to Designing & Programming

Establish a baseline against which the effectiveness of the workshop may be measured

Customize our workshop based on specific areas identified in this assessment

Pre-Assessment: Before the workshop, we’ll send a problem description, your developers will spend max 4 hours and solve the problem and send us the code. We’ll evaluate the code and send you detailed feedback about the code, including areas for improvement. We can send different types of problems (fresh development, cleaning up existing code and so on.)

Post-Assessment: 2 week after the workshop, we send another problem and evaluate the solution code. A comparison between the Pre and Post Assessment should be able to clearly quantify per-participant level improvement.