air – web application (UX)

A quick snapshot of some of the UX methodology we adopted while building and designing air. The app was built using an Agile Scrum methodology. Where by the goal is to develop, deliver, and sustain complex products through collaboration, accountability, and iterative progress.

Sprints were used to build the software. Each Sprint lasted no more than a 4 weeks. Our Scrum master and Product Owner roles where picked up by our PM and Lead Developer. We only had 3 people in our Development Team. Each Sprint consisted of Sprint planning, Daily Scrum, Sprint review and a Sprint retrospective. We got better at this process as the project progressed. Workflow software Trello was used to help organise the team. We were each assigned tasks to complete on a weekly basis. Trello help to show progress and bottlenecks that needed addressing. A backlog was created.

User stories were created and then placed into Epics when necessary. The Epics then dictated the Sprint order. User and system flows were produced with myself and the lead developer to better understand the end goal. From this I started to create low fidelity wireframes (sketches) and then high fidelity when needed. Sketch was used for designing the concepts and final designs. We used Invision to quickly preview designs for mobile and desktop.

The initial air team was just three people originally. Myself a talented Lead Developer and PM. The team was set up after the ‘air’ timescale had been created. Two of us had yet to be hired. This was the cause of much stress and frustration in the middle of the project. The app had to perform several complicated functions which by themselves would have taken up all the time allocated. However after much blood, sweat and yes tears we achieved are deadline of launching air to our first client.

Certain methodologies have now been adopted by the wider company to improve work flows and other software projects.

ClientImpactYear2018ProjectWeb app UI, UX & branding