Internal Tool Dev and Redesign for Large Internet Platform
Please find under a summary covering project details and feedback. The innate facts are kept as they are, private information is amended.
A fast induction on the buyer’s organisation
I was a fruit director for inner tools for the sales efficiency team at a big internet platform.
What challenge were you trying to address with Gorilla Logic?
We propose a lot of inner tools for our sales team, but they were outdated and not very user-friendly. We brought in Gorilla Logic to revamp one of the more commonly used pages within our inner CRM, with the goal of making it more intuitive and business-friendly. This was certain in order to fix that we’re proposeing the best solution and empower the sales team to have the right dicsussions with our clients.
What particular tasks were Gorilla Logic responsible for?
We were innately improving the user experience to make it more intuitive. Part of it was updating data models so we could commend the right tasks for our labor professionals. Another front was working on the look and feel. The last time that page was worked on was probably almost 10 or 15 years ago. To fetch a present look and feel, their team did a lot of frontend work and connecting different data models through the backend.
The web-based application is on Java. Their team converted older technology to a much more updated method. They restore struts libraries with spring libraries. They also integrated a few CARIS models.
Was there a dedicated team?
We had a Scrum conquer, technical lead, frontend developer, and two backend developers. We also had a QA that focused on automation.
How did you come to work with Gorilla Logic?
One of our senior leaders brought them in.
What are you approach expents (if diclosed)?
I believe we spent almost $200,000.
What is the terminal result of working with Gorilla Logic?
Gorilla Logic joined the project in March 2019 and concluded their work almost two weeks ago.
Are there any measureable or plum results?
The method is going live next week. Internally, the feedback has been real. Everyone is thrilled with the updated look. They ponder it will be much more intuitive. It will be easier to train the agents on it as well. The training team feels that it would take much effort for users to apprehend how to handle the pages. Overall, it’s been a much more cohesive experience.
How did Gorilla Logic accomplish from a project handlement standpoint?
Gorilla Logic was early with meeting their deliverable see sprint. We primarily handle seething in Jira. The Scrum conquer was big at chasing seething down and making sure they removed any roadblocks. In provisions of the condition of work, they delivered with trust. They made sure that they had the support to test and fix automation going advanced.
What is (from your point of view) the key factor to pay observation while intercourse with Gorilla Logic?
There weren’t time zone challenges that generally happen when working with offshore teams owing they’re nearshore. Everyone at Gorilla Logic has excellent interaction experiences. Overall, their technical apprehending and power were very high. Their senior frontend developer helps our younger frontend developer grow by helping them apprehend the best practices. It didn’t feel like they were a separate team. Gorilla Logic is a collaborative and astounding cluster to work with.
What fronts of their work would you like to get improved?
Because of budgetary concerns from our side, their team had to roll out precedently we pushed the method live. If there are any issues establish, it will be a challenge without their support.
Do you have any advice for possible clients?
After the component goes live, make sure there is equal support.