Definition of Done

Welcome to the Jira for Designers series brought to you by Design at Scale™ — Academy. In a previous article, we discussed the Definition of Ready and how it impacts delivery within the in-house and remote teams(↘︎Link). This article will look one step further at how designers support engineers in delivering the proposition and integrating it with the outside world. Undoubtedly, from time to time, some designers have the tendency to own things when they do not need to.

Process

If you believe that the DoD — Definition of Done(↘︎Link) is written for designers, you are making a mistake. This definition is mainly for our engineering colleagues, where the design function becomes purely supportive.

In the first phase, we all co-define proposition. In the second phase, we designers co-create user acceptance criteria, functional and non-functional requirements, and other pillars of software development. This face is mainly about the contributions of designers and developers. In the third phase, the ratio of support and leadership exchange is from 80/20 to 20/80, and the leading position of design moves into the peripheral supporting function. While our engineering team delivers the code, we…