bdd advantages and disadvantages

1BDD advantages and disadvantages
2
31. BDD is focused on discovering and developing
4features that brings high business value, 
5so any feature that does not bring value will be ignored.
6
72. Because of the reduced waste,
8the development  process will be focused 
9just on the features that matters,
10so any additional cost is reduced.
11
123. The requirements changes will be easier 
13to implement because of the living documentation
14and safer because of the executable specification,
15which will act as automated acceptance and unit tests.
16
174.The releases will become more frequen
18t as the large number of automated tests
19will eliminate some of the manual testing
20done by the testers. The testers will have
21more time to focus on other more complicated
22tests and scenarios.
23
24The main BDD disadvantages are:
25
261. BDD practices are very focused on discussions
27and collaboration between all parties involved.
28In case the business owners are unwilling or
29unable to engage in conversions and give
30feedback in time, then it will be hard
31to take advantage of BDD.
32
332.One of the BDD principles assume that
34it is very hard to know all the requirements
35from the beginning and that we don’t have to
36define them all in the first phase of a project,
37but instead the knowledge of the stakeholders
38will evolve during the lifetime of a project.
39That is why it is considered that BDD is well
40suited to be used in conjunction with Agile 
41
423.In some cases, for example large projects
43developed by corporations, which delegates
44the work to multiple remote teams, will be
45harder for them to enable the
46high collaboration between teams.
47
484. For some complex applications,
49it will require experience to design
50and write the automated acceptance tests.
51In case the application will acquire many
52poorly written tests, they will become hard to maintain.

1The main BDD disadvantages are:
2
31. BDD practices are very focused on discussions
4and collaboration between all parties involved.
5In case the business owners are unwilling or
6unable to engage in conversions and give
7feedback in time, then it will be hard
8to take advantage of BDD.
9
102.One of the BDD principles assume that
11it is very hard to know all the requirements
12from the beginning and that we don’t have to
13define them all in the first phase of a project,
14but instead the knowledge of the stakeholders
15will evolve during the lifetime of a project.
16That is why it is considered that BDD is well
17suited to be used in conjunction with Agile 
18
193.In some cases, for example large projects
20developed by corporations, which delegates
21the work to multiple remote teams, will be
22harder for them to enable the
23high collaboration between teams.
24
254. For some complex applications,
26it will require experience to design
27and write the automated acceptance tests.
28In case the application will acquire many
29poorly written tests, they will become hard to maintain.
30
31ON THE OTHER HAND 
32
33BDD advantages 
34
351. BDD is focused on discovering and developing
36features that brings high business value, 
37so any feature that does not bring value will be ignored.
38
392. Because of the reduced waste,
40the development  process will be focused 
41just on the features that matters,
42so any additional cost is reduced.
43
443. The requirements changes will be easier 
45to implement because of the living documentation
46and safer because of the executable specification,
47which will act as automated acceptance and unit tests.
48
494.The releases will become more frequen
50t as the large number of automated tests
51will eliminate some of the manual testing
52done by the testers. The testers will have
53more time to focus on other more complicated
54tests and scenarios.