In this interview, Neeraj Tripathi, vice president of Global QA at Infor, goes over the principles of effective software quality management. He explains how to measure customer satisfaction and how active QA involvement eliminates defects early and shifts quality left.
Josiah Renaudin: Welcome back to another TechWell interview. I’m joined by Neeraj Tripathi, the VP of Global QA for Infor. Today we’ll be speaking on the principles of effective software quality management. Neeraj, thank you for joining us. First, could you tell us a bit about your experience in the industry?
Neeraj Tripathi: I have been in the IT industry for more than twenty years now. I was fortunate to start my career with IT consulting companies. Working for these IT consulting companies allowed me to work with different clients and domains, spread across the globe with new problems and challenges to solve. Working with many clients on different stages of project/program also allowed me to do software development, project management, onsite/offshore sourcing strategy, and building QA COE.
Couple of years back, I got an opportunity to set up a QA organization from the scratch for one of my clients in the US and after successful completion of that assignment, I continued to get many more opportunities to build independent QA organization or set up TCOE/QA COE. One of my recent jobs was to lead and manage 700 or more QA organizations for the Fortune 10 company, where I centralized the entire QA organization spread across different LOBs and developed mature shared services organizations with pre-defined SLAs and KPIs.
Josiah Renaudin: How do you effectively measure customer satisfaction, and what do you feel are the best methods for not only meeting expectations, but exceeding them?
Neeraj Tripathi: There are many ways customer satisfaction can be measured based on products and offerings you have in the marketplace. Key customer satisfaction metrics are customer retention, reduction in clients facing issues, and repeat customers. If you are getting customers referrals, then you are certainly exceeding expectations. Quality of your products and the ability to fix issues quickly both play vital roles in all of this.
Josiah Renaudin: Can you define what you find to be the ideal “enabling environment,” as well as how to properly celebrate or promote success?
Neeraj Tripathi: I think the ideal enabling environment is where resources are aligned with the organization’s objective, motivated to do the right thing and they have adequate resources and support available for them to do the job. Celebration is one of the key aspect of building enabling environment and believe me it is not difficult and should be done by breaking down large and long term deliverables into short term milestones & accountability to provide sense of accomplishment and recognize resources for their effort and leadership.
Josiah Renaudin: Nurture empowerment is a term you’ve brought up in the past. How often have you seen management fail to properly recognize team members, thus reducing the team’s overall effectiveness?
Neeraj Tripathi: I would say very often, and I might have done the same in my career. What I learned and would like to share is that while recognition is important, what is more important is to share the actual effort and behavior this resource or team is recognized for. If we are not clear in our message and not consistent then we risk reducing the overall effectiveness of the organization.
Josiah Renaudin: How can active QA involvement both eliminate defects early and shift quality left? How early should the QA team get involved?
Neeraj Tripathi: I think the answer is simple: that QA should be involved starting during the requirement phase. What is lacking based on my observation is “active QA involvement.” I’ve seen QA get involved by attending requirement meetings, but if they do not have any tangible deliverables from those meetings, then those meetings are not productive and QA teams miss the boat to understand, challenge, and evaluate requirements for testability and/or contribute for better requirements.
By finding defects in the requirements, design, and development phase, teams not only eliminate defects early, they shift quality left to apply quality measurement and defect elimination from the testing phase to early phases of the SDLC.