Mobile App For a Food Industry Behemoth

After assessing the clients' requirements and defining the functionalities to be implemented, we put together the team to take the project forward. The next task on hand was to get started with developing the mobile application. We had daily sprint calls with the client to understand their requirements and assess how to implement them for a smooth user experience. Before each sprint, there was a planning call along with the developers where the client would provide the entire walkthrough of the tasks planned.

We also held daily scrum calls with the client,  where we discussed three main queries regarding what was done, what remains to be done and discussed solutions to impediments which were in the way, if any, as well as the status of the above-mentioned queries were discussed with the client. We also had sprint review calls with the client each evening, where they discussed the sprint progress in detail, in case of any blockers. As a part of the sprint review, we shared an executive summary with the client on a monthly basis and reviewed the burndown chart in order to understand the team velocity.

Since the client wanted us to develop the Frontend of the mobile application using the same codebase for the nine apps they already had, we decided that the best way to take this forward is to use NativeBase components. The third version of NativeBase had reusable UI components built on top of React Native, which supported the client’s decision to implement the same codebase. The client handled the design phase and they provided us with the Figma designs for the screens and tickets were generated using the Azure board. Since the project required us to communicate extensively with the client to understand their requirements, we decided to use MS teams as the communication platform for the project. 

After the successful completion of each sprint, we also conducted hour long sprint retrospective sessions, along with the client and in the call, we discussed what went well (to keep doing these things), what could be improved (went OK, but could be better), and what to avoid (to make the necessary changes). We considered this feedback and started implementing them for the next sprints.

It was pertinent to see that the development phase was progressing without any glitches that would hamper the project's quality. We employed a QA analyst who conducted extensive tests for every feature using BugSee, a bug tracking tool that could detect any crashes in live apps. Since the platform was built on top of React Native and NativeBase, the QA analyst also conducted checks for iOS and Android platforms by setting priorities for end-to-end testing and specifying the test cases using ALM. We also used MobX as the state management tool of choice to decouple the code and manage the application's state outside of the UI framework.