A Guide for Implementing the Behavior-Driven Development (BDD) Framework in IT Projects
Budihal, Avinash (2025)
2025
All rights reserved. This publication is copyrighted. You may download, display and print it for Your own personal use. Commercial use is prohibited.
Julkaisun pysyvä osoite on
https://urn.fi/URN:NBN:fi:amk-2025052616485
https://urn.fi/URN:NBN:fi:amk-2025052616485
Tiivistelmä
The thesis looks into the issues that come up when agile IT sector companies adopting Scrum try to write executable test cases from user stories whose core focuses are behavioral needs. If requirements are unclear to all parties, people involved in the project may misunderstand each other, and delays can happen, leaving more issues inside the software code. Therefore, the purpose of this study is to develop a step-by-step guide for Scrum teams to start using the Behavior-Driven Development (BDD) Test Framework.
By using behavior-driven acceptance criteria, BDD helps people on the scrum team to understand the requirements the same way. Discuss and agree on the rules for the project to let each person understand their duties and the tasks involved.
It also uses information gathered from talking with people who are actually trying out BDD with their Scrum teams. Many points in this paper were drawn from interviews with experts involved in the Scrum team during BDD. Experts looked over the first proposal to help perfect and finalize the document.
The thesis was developed by studying real cases from companies and advice from specialists in the field.
The goal of this thesis is to show organizations how they can improve their test cases, better meet user expectations, promote stronger teamwork between development, testing, and business teams, and supply software that fully fits the requirements of agile.
By using behavior-driven acceptance criteria, BDD helps people on the scrum team to understand the requirements the same way. Discuss and agree on the rules for the project to let each person understand their duties and the tasks involved.
It also uses information gathered from talking with people who are actually trying out BDD with their Scrum teams. Many points in this paper were drawn from interviews with experts involved in the Scrum team during BDD. Experts looked over the first proposal to help perfect and finalize the document.
The thesis was developed by studying real cases from companies and advice from specialists in the field.
The goal of this thesis is to show organizations how they can improve their test cases, better meet user expectations, promote stronger teamwork between development, testing, and business teams, and supply software that fully fits the requirements of agile.