Blog's View

WEM Starter Experience

Penned By -

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 are communicating with stakeholders across the board, including customers, business managers, and the development team to make sure the goals are clear and the vision is aligned with business objective.

We worked using SCRUM methodology. The route I took to start with this project was to first check the backlogs. We prioritized backlogs and moved on to creating a sprint. We are following all the SCRUM ceremonies, which are:

1) Sprint Planning - Sprint planning sets up the entire team for success throughout the sprint. Coming into the meeting, the product owner will have a prioritized product backlog. They discuss each item with the development team, and the group collectively estimates the effort involved.

2) Daily SCRUM - Stand-up is designed to quickly inform everyone of what's going on across the team. It's not a detailed status meeting. The tone should be light and fun, but informative.

3) Sprint Review - Sprint review is a time to showcase the work of the team. They can be in a casual format like "demo Fridays", or in a more formal meeting structure

4) Sprint Retrospective - Retrospectives help the team understand what worked well–and what didn't.

To create a backlog, I had to understand the technology well, hence I started undergoing the WEM training along with the development team. We started our week-long WEM training by watching an introductory YouTube video, followed by the online training after which we started to implement our learnings. Five 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 –

1) In WEM, We generally face issues in expressions in the initial stage. For example, if we wanted to add some condition or calculation for any field then we needed to write an expression. We faced normal expressions issues in the starting for training till 3-4 weeks.

2) As some of the team members were not developers, API integration was a big challenge for us. Right now, everyone can create and integrate an API.

3)On the design side, we started to focus on creating user-friendly designs.

4) On the design side, we started to focus on creating user-friendly designs.

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 the 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 this project, I 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. We faced challenges regarding entity connection in the initial stage but we came on track after the first review. This is 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 activities like add, edit, delete, activity log, import, and export – which they took 2-3 days to create. Once they were done 3-4 master data after that 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 an API access point that 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 and it should be done in a week's time.

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.