Last updated: 23 March 2018
The high quality of our platforms is a task that every team member is responsible of. Use this guide to learn how the Design team promotes quality assurance practices during the whole life of a project.
The Sprint designer must make sure that:
A designer from the team must 'adopt' the project, as an official supervisor. Each designer should then be able to engage in an average of 2 projects at a time; and that involvement implies she makes sure of:
Take one or two weeks (at least) to work exclusively on the project's interface. This work implies:
Afterwards, take one or two weeks (at least) to generate front end code base. The main focus should be:
Considering that the designer will not be able to assist during the full development process, after her initial involvement she will seek to run at least 3 Design Reviews with the developers.
In each one of these reviews (spread equally over the time left before deployment) the designer will evaluate:
Bugs and possible enhancements will be documented and prioritized, so that the developers fix every suggestion (with or without the help of the designer).
During the last week of the project (before final presentation with the client), the designer will engage closely with the development team to make sure that no one is missing any critical detail that hurts the quality of our delivery.
This engagement implies:
Specific formats and practices described in this guide are in constant evoution. Make sure to check in with the current Lead Designer to obtain better details and references.