Behavior Driven Methodologies

Evolving from waterfall to Agile Behavior Driven Methodologies?

One of the main problems is the slowness response to changes.

The time spent through requirements definition, analysis, design, implementation and testing to end up with a working product, has been a common problem that has led teams to"not in the picture"results. Ring any bell?

Multiple technologies, changing requirements, challenging reality ... The number of factors, that affect the performance of software teams, is constantly growing.

No matter what side you feel identified with, the wrong process will cost thousands of dollars to the project/organization you’re working for. BDD aims to solve those problems by creating more harmony between the user story practices from Scrum and the Test-Driven Development practices from XP. The user stories practices represent analysis and specification in agile projects and Test-Driven Development represents software design.

still some unsolved problems?

• Communication

• Collaboration

• Quality issues

• Regression analysis

• Traceability of requirements

BDD promotes teams to discuss Acceptance Criteria, and ensuring that teams fully understand the business requirements. BDD offers more precise guidance on organizing the conversation between developers, testers and domain experts. This moves team members to think through solutions, before starting to write code. Everyone in the team is in the same page and improves their knowledge of the product they are building.

While still BDD is not widely adopted, teams using this process have experienced significant improvements on communication, collaboration and quality of the software delivered, last but not least...a highly grade of satisfactions of stakeholder expectations.

What do you think, will you manage software development projects with BBD in your company?