Ask Our Experts

Join our discussions! Ask our experts how you can leverage technologies like AI and ML, big data, and blockchain, in your products. Our subject matter experts give actionable suggestions to mitigate technological challenges and accelerate your product roadmap.

mukund rajamannar
Mukund Rajamannar
Director of Engineering Services
Synerzip tenure: 10 years
Certified Scrum Master

Mukund Rajamannar is a seasoned web and mobile architect and the Director of Engineering Services at Synerzip. His specialties include building teams for taking products to the market and mentoring teams for growth. Throughout his professional term, Mukund has worked on architecture and design with teams to build horizontal scalable and performant product solutions with a service-oriented architecture. He has also built development teams focused on continuous engagement and delivery using open source and cloud services.

Mukund’s current focus lies in helping clients realize their Data Science, Big Data, and AI product dreams in a cost-efficient manner.

   

Talk to Mukund

Need a question answered? Our experts are here to solve your technology and business challenges. Keep checking back to view recent discussions and trending topics. You can also reach Mukund directly by clicking on the email link at the top.

  • This field is for validation purposes and should be left unchanged.
Recent Discussions

Can you give us an example of the importance of Agile and its roles?

In quite a few organizations, a single team member may play multiple roles without being defined. This can cause problems. An example of a product manager comes to mind. S/he is responsible for implementing product success and ensure that it is monetized and holds up to its vision. However, many clients do not have this role defined. After coaching them through it, they realized the value acceleration a well-defined role can cause.

Can you list a project where Agile roles were defined and how it impacted the product?

I want to talk about the role of a product manager in a healthcare setup. One of our clients’ uses technology to accelerate the process of clinical trials. While he is a visionary in this field and has extensive domain know-how, he could not translate it into a product process. This is where our product manager stepped in, liaised with him, and translated the vision to a product strategy. The product is now running trials in remote parts of the world.

What are your thoughts on DevOps in the Agile world?

Many of our clients have a cloud-native strategy, and they are aware of the services cloud providers offer. However, there needs to be a role that monitors the new and upcoming ways of securely deploying the application in the cloud, securing your source code, and optimizing cost. You cannot combine this role with that of a developer who is more focused on building functionality.

Hence, DevOps’ role is crucial, especially for clients who have a cloud-native approach for their applications. For example, we recently worked reduced costs for a client whose products offer video streaming analytics. When we added a DevOps member to the team and who knew how to run applications at scale, the costing came down by about 50%.

In your opinion, which roles are critical for success?

The product owner plays a crucial role, in my opinion. S/he is responsible for the overall success or failure of the product. Another recent trend that I observe is that development teams do not feel the need for QA. However, I think QA is a critical role because it helps developers focus more on developing functionality. On the flip side, I don’t think there is a significant risk because of a missing role. However, it depends on the core team and its composition.

Do you think Agile helps the organization move forward?

Yes, I do. It helps the team be better, but it also helps the management look at risk areas at a collective level. In the analysis of building products in the last couple of years, we’ve identified specific roles and responsibilities that are absolutely needed from an Agile perspective. Hence there is some validation for the risks documented in the checklist. It also helps us talk to our customers and explain why certain things are happening the way they are and how they can do better.