Ozan

Analysis

As part of the analysis, we identified what features the stakeholders wanted in place, as well as how other companies and banks handle the same problems. Different combinations and flows were presented to the business owners. Edge cases (such as delivery failed) were included as part of this process. Technical architects were present throughout, ensuring all features were feasable.

UX & UI Design

Different user stories and personas were created, and tested from the point of view of internal and external users. We then found the best process that gathered all required information while still being user friendly.

Low fidelity wireframes were created, tested, until imperfections were ironed out. Following that, documentation and a high fidelity prototype was created.

A few photorealistic options for physical cards were presented to the client to choose from.

Development and testing

Before starting development, technical discussions determined what could be split into small blocks and reused. This led to faster delivery and a more maintainable codebase.

Realtime updates were provided by ticking off tasks one by one within JIRA, for the product manager to monitor.

Analysis

GAP analysis We identified gaps with the product manager, and backend team. As a result, new tasks were added to the backlog for monitoring.

Development and testing

A lot of upgrades were free as they were delivered alongside features or bug fixes.

Realtime updates were provided by ticking off tasks one by one within JIRA, for the product manager to monitor.

We reduced complexity by removing repetition and thousands of lines of code.

We improved maintainability by adding type support, splitting up features using atomic structure, and using redux across the board.

Code quality

Code reviews and automation were used to improve quality. Unit tests were not built as resources were short. However, a QA team constantly monitored and built E2E tests for the project.