Osmee App

An application to manage all the consultants of an ESN.

The challenges

This application must be the only point of information exchange between the consultant and the ESN for rncrease service to consultants and centralize information in one place. 

This should accelerate business processes to save time and optimize company resources.

A technical team, a product owner, a scrum master and a team of 3 graphic designers under my direction were mobilized on the project.

Introduction

Creation process

To carry out this project, after having collected a general vision from the business staff, our team turned to the Scrum methodology for the development of the project.

1.

Vision and User Stories

The vision of the project was defined following interviews with the business team and the consultants (users) concerned. 

Then this vision was broken down into several User Stories and sorted according to the MoSCoW analysis.

That's when I stepped in to help our UX designer.

2.

Backlog

The User stories sorted in the order of their importance allowed us to build a general backlog. 

The Scrum Master and the Product Owner were then able to split everything into several sprint sessions of 2 weeks each.

3.

Sprint Design/Dev

The sprint is divided into 2 parts: the Design sprint followed by the Development sprint. 

The 2 weeks design sprint started with the Benchmark of the expected features, followed by a user navigation flowchart, zoning on Whimsical, wireframe and mockup on Figma, test of the mockup with the business.

4.

Delivery

I was in charge of the quality of the model provided by the team as well as of all the technical documentation.

Each sprint presses a version 1.x of the application. Due to financial difficulties the development of the platform unfortunately stopped at version 1.8. However, our tool has already proved its worth: the company's financial resources and the daily workload of the business have been optimized considerably.

Project toolbox

Jira Software-blue
Confluence-blue

To save time, our technical team started with the Element UI component library in JS view. 

To be able to work on these elements, the first task of the design team was to build this library with Figma components.

From version 1.3 onwards, we abandoned the library to build, together with the technical team, our own system of interface elements.

We worked on more than a dozen Figma pages, and we quickly discovered that the work plan has its limits in terms of space and can sometimes be tight.

We needed 7913 elements on Whimsical to create our user stories, flowcharts, mind maps, wireframe, tables etc. to define the basis of our project and get off to a good start.

We participated in more than 8 sprints in Agile and the design team solved more than 200 problem maps and user stories. I was responsible for the creation, naming and validation of each of these maps.