Behaviour Driven Development for Designers.

Welcome to the Jira for Designers series brought to you by Design at Scale™ — Academy. In a previous article, we discussed Confluence as a knowledgebase(↘︎Link) complementing the Atlassian Jira Board(↘︎Link). This article will examine the two types of development and why it matters to designers like yourself to see the difference and what you can get out of it.

Disclosure: Please keep in mind that my development knowledge is limited, and my ambition is not to copy and paste what is elsewhere — but to merely introduce these methods and allow designers like yourself to ask the right questions. If you are an engineer, you’ll laugh a little — so let’s begin.

Development types

It is quite obvious that over the last fifty years, development, the same as other disciplines, has gone through a biblical revolution. Therefore, our engineering colleagues have experienced, tested, used and ditched several different types of development approaches. More robust systems required extensive testing, which led to a method called test-driven development. Many fronts and groups reflect on the use of behaviour models and adapt to the framework called…