Singing from the same hymn sheet.
You may have experienced one of the major causes of IT project failure: disconnect between the business’ requirements and what’s delivered by an IT solution provider.
Agile development practices, which we follow, are now commonly used in the industry to eliminate this disconnect. Examples include regular “show and tells” during product development, embedding business stakeholders in the team, short development cycles and frequent releases, etc.
However, the most important part of a project is getting the correct requirements in the first place and then ensuring that all members of the wider team understand those requirements.
To achieve this, we’ve adopted Behaviour Driven Development, known as BDD. We now capture all project requirements in simple scenarios, which follow a consistent given-when-then pattern. An example is below:
Given I add a flight to my basket.
When I press the update button.
Then the total cost displayed will be updated.
Because these scenarios are simple, all those involved with the project (stakeholders, analysts, developers and QA testers) can understand them and, because a consistent format is used, there should be no disconnect between what’s expected and what’s delivered.