I am sharing my first project experience, where I had the role of a business analyst – managing the project in Jira as scrum. My roles and responsibilities were to understand the technology and requirements.
The route I took to start with this project was to first check the backlogs and urgent tasks which are on priority, following which I moved on to creating a sprint and carried out all the scrum ceremonies – Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective.
To create a backlog, I had to understand the technology well, hence I started undergoing the WEM training along with the development team.
The WEM training started with us watching an introductory YouTube video, post which we started the WEM online training. The training was completed within a week, after which we started to implement our learnings.
Multiple teams were created with two members each and had picked up an idea for a project like Employee management, Project management. Initially, the team started facing the following challenges –
To help us solve these issues, we were assigned a WEM expert who guided and mentored us at every step where we got stuck. We started with having a check-in call every 3-4 days, and discussed challenges faced.
Once the WEM training and test project was completed, I started working on a practice travel project. Where we created stories and a sprint as well.
For that project, I have created an ER diagram with the team. In WEM, if you have clarity regarding the data model then you can easily execute a project. Once we finalised the ER diagram for our project each team member had taken one/two entities and started work on the data model. With a lot of ease, we were able to create a database for our project. Sharing the ER diagram of our project.
Post that, we created a master data for reference. Each team member had taken one master data and performed add, edit, delete, activity log, import, and export – which they took 2-3 days to create. But soon we escalated our speed and we completed one master data in a day.
After that, we implemented a search bar so the user can search and view all available flights for a source and destination. We integrated an external API to show search results. A challenge arose regarding dynamic JSON key mapping because in WEM, you can’t do the dynamic JSON key mapping. Hence, we made an adaptor on AWS which is actually an API access point which triggers lambda. Lambda calls the actual API for flight search and formats the JSON response with static keys. That really helped in solving our problem.
The user can search a flight to enter the source, destination, departure date, return date (for the round trip) along with a select number of passengers. Once users click on search then the flight lists are visible as per search results. Currently, we are working on the booking creation part.
In our organization – Prodt, every team member now knows the development and usage of WEM. Our designers, business analyst, testers along with our Director are now capable of developing an application on WEM with a lot of ease.