STORIES OF ENABLE EMPOWER EXEMPLIFY
STORIES OF ENABLE EMPOWER EXEMPLIFY
Naga Satya Lakshmi Kalyan Allam
COVID-19 dashboard
Kalyan’s team built a COVID-19 dashboard and showed it to our customer contact. She, in turn, took it to her boss. As Kalyan’s team was already hard-pressed for time, the customer told them to put the project on the back burner. However, his team persisted and did that as pro bono work. His team ended up building a good dashboard in two months. Now, it is a significant revenue-making dashboard for our customer, and has expanded to seven other dashboards
Tamil Bharathi
Creative prospecting
Zuci got this lead from a conference that we participated. But it went cold after a point in time. Still, the sales resource kept in touch with him. Finally, he wrote a mail stating that if he gets a response from the prospect on the weekend, he will treat himself to a beer during the weekend. The prospect asked him to treat himself to a beer, so a meeting was set up for Monday. They are our customers now.
Fidelis Rodrigo
Stakeholder collaboration
A seemingly unresolvable issue popped up in one of our projects that the client gave up on after hitting a major technology roadblock. Fidelis refused to accept defeat and burnt the midnight oil for the next 3 days to find a solution to make it work. We woke up to see him have achieved the impossible on the third day. The client was obviously ecstatic and a Zengineering moment came to life. Fidelis’s attitude that night is an example of everything Zuci stands for.
Dhanalakshmi Tamilarasan
Non-functional aspects – all the time!
At Zuci, we don’t stop at functional testing, but as a practice, testing team also ensures that they examine the non-functional testing aspects, even when it is not a direct ask from the customer. Anytime Dhana’s team is tasked with ensuring the functionality of a customer’s product, her team takes ownership of the product and assesses the non-functional aspects like performance, security, and then recommends the development team on the modules/areas of improvement. Now, it’s one of the ways her team empowers the customers’ products to thrive through release.
Pavithra Seshadri
Honing the team’s strengths
Zuci had a challenging project for a customer that required a mix of skills. The skills needed weren’t easy to find. A team of two, led by Pavithra, was working on Phase I of this project, filling the shoes of five resources. Collaboration was a challenge. Her team’s Friday lunch and coffee sessions helped break the ice by knowing her team better and identifying each other’s strengths. This helped in proper work allocation and project delivery.
Balamurugan Vellaichamy
Learn and Implement
The customer wanted to develop a ticketing system. While the project was not complex, they wanted Bala’s team to implement a pretty new framework. Considering past experiences, the customer had decided to partner with Zuci. Bala’s team quickly did the learning and cracked the technology pieces to start the development sooner. The team went beyond the expectations and suggested a container (Docker) that provided the capability to test once and deploy anywhere. This ensured that the application did not have any issues during production and reduced its time to certify for different environments.
Hamna Thottumugath
Onboarding 100+ resources within a few months
Recruitment challenges are typical for a growing start-up. At Zuci, the complications multiplied when the HR team was looking at onboarding many Zengineers within a few months. However, Hamna looked at recruitment challenges as possible opportunities, flipped the onboarding processes a bit, and provided an experience that the candidates would not forget. Her team ensured that the entire interview process got over within a day, offline or online. Every individual gets feedback and offers within 48 hours from the time the engagement starts—the reason why Zuci was able to onboard so many Zengineers in the last four months.
Saifudeen Khan
Getting into Customer’s shoes
Covid 19 induced lockdown had all the businesses think of alternate options. Saif’s team was stuck as they couldn’t access the client’s systems and servers working from home. Saif’s team rewrote the project planning documents explaining what is possible from remote, their dependencies on their on-premise system that aren’t accessible, and how this would affect the delivery timelines. This helps Saif’s team identify portions of work that could be handled remotely and diligently work on those. In the time that has passed, the team’s relationship with the client has evolved. The trust gained has made the client relax their security policies, and the work has generated speed.
Aswin Francis
Collaboration and curiosity
When Aswin’s team of 4 started to work on the project, all the knowledge sharing was done over chats and calls, and they documented all of it in Wiki for future references. Through this collaboration, the entire team was up to speed in no time. When working on the project, they talked about the solution implementation, how it works, and what is going on behind the framework. This allowed his team to share their wisdom with others and any relevant articles that they come across. Today, they have an internal wiki that has more details about the products than what the customer has.