top of page
Weaver
Context
Employed
Role
UX / UI Designer
Year
2022
Weaver was initially named ReqAsCode corresponding to the squad in charge of developing the toolchain in the client project. ReqAsCode comes from writing requirements as code because the objectives was to allow people used to the development environment to stay in their environment and be more comfortable. Indeed, the development activities of system, software, safety, security, requires to write requirements and to make a circuit of review, correction and validation with other profiles who are not always used to the development environment.
The project had already started when I joined it, integrating a team of developers well established in an agile method dynamic at the fourth cycle. Unfortunately, the previous interviews were not saved and the note-taking was not very readable and difficult to use. So we had to do almost everything again.
I undertook to recover as much as possible of what had been done and carry on with the interviews of the profession profiles. I was able to do about ten interviews and a questionnaire on the review and comments part. All the transcripts and data collected were written and capitalized in the shared tool Miro.
It was requested to provide a research review file including personae and enough content to be self-supporting. For this project, there were many personae because each reviewer profile had its own particularities and needs.
Then I made wireframes to test the way to comment and interact in the requirements document. I had to follow the layout of the opensource tools that the team was using according to the needs of the product owner. It was tested by three different users. Finally, I started to produce the mock-ups by integrating the client's design system.
Unfortunately this mission had to stop for me because a team in the company was taking place and as I was a consultant, it was better to favor the employees. Finally I finished this mission by creating a logo with the team with different workshops based on the name they had chosen together for the product: Weaver.
What was the most complex in this project was to do all the analysis phase late since I joined the project along the way, but especially to provide elements to the developers following the objectives of the sprints while I was still collecting data. It was a challenging project with a great learning experience.
bottom of page