2. My identity
▪ Ramkumar ‘Ram’ Ramachandran
▪ Captive IT unit of Euro-Japanese Automobile Giant
▪ GM – Quality & Testing
▪ Global Service Delivery viz. US, UK, China, Singapore, France,
Thailand, Taiwan, Philippines, Bahrain, Kuwait etc.
▪ Aeronautical Engineer / IIMC Alumni
▪ CSQA, CISA, PMP, SAFe Agilist
▪ The content is purely out of my personal experience and is not
out of any research conducted by me or anyone else
▪ Approaches provided here would work in most of the
scenarios, but the organizational culture would be a major
4. What’s inside!
▪ Why this conflict?
▪ The Communication Gap
▪ What Senior Management ‘Actually’ Wants
▪ The Business Influencers
▪ Process Ownership
▪ Take the Risk Route
▪ Build the Right Team
▪ Invest in Innovation
5. Senior Management Commitment
We have zero-tolerance to bad quality…!
The biggest investment we have
made in our organization is on
We don’t mind having a bad
customer to whom we have
delivered good quality
Quality is Numero-Uno
parameter for all of us…!
We don’t mind bending backward to bring in
quality in our services
We will not bill the customer
for any proven bad quality
6. Why this conflict, when quality matters most?
▪ In IT industry Quality Models are ‘evolving’
▪ ‘Waste’ is not evident
▪ Rules could ‘significantly’ vary based on domain & technology
▪ Revenue leakages not tracked effectively – Rework / Low Productivity etc.
▪ Quality Professionals do not appreciate technology – Well, Mostly…!
▪ A crowd out there, harps on documents – for proving quality…!
▪ Super Heroes / Pockets of Excellence encouraged
▪ Systems that suits West implemented in Indian IT companies
11. Map Business Goals to ‘Influencers’
• Good delivery model
• Less Rework
• High through put
• Consistent Good Deliveries
• Vendor Responsiveness
12. Delivery Owned Process
▪ Engineering Process Group SHOULD be owned by Delivery
▪ Quality Team brings global best practices into QMS
▪ High visibility to Senior Management on EPG activities
▪ No cribs: -
– ‘It’s QA Team’s processes’
– ‘This process doesn’t fit me’
▪ Quality Team ensures that there is no ‘undue’ dilution of controls
13. Take the Risk Route
How do you bring in consistency in
delivery operations across team?
If a delivery is made successful without practicing
process, how to replicate success?
How do you know the un-reviewed code
is the most optimal one?
This project looks to be cooking up documents for audit, which will
have sustenance issues
There seems to be too many inter-sprint
changes, which will make application
Late deliveries to Testing are eating into regression, which could lead
to heavy defect leakages
The Product Owner is evidenced to have
limited domain knowledge, which could
lead to UAT issues
Doing a Fixed Bid project under iterative model will
lead to huge revenue loss
14. Formal Communication Channels
Operational Inputs to Delivery Teams
Tactical Inputs / Alerts to Delivery Heads
Strategic Project / Program Risks to CEO
Delivery Excellence Head
15. Build the Right Team
▪ Team that ‘thoroughly believes’ quality
▪ Team that appreciates ‘Delivery Nuances’
▪ Team Leads / Managers who are strong Communicators
▪ Team Leads / Managers who can ‘see beyond the obvious’
▪ Managers who can ‘make a point without making an enemy’
▪ Team that ‘learns continuously’
▪ Team that can outgrow their role very quickly
16. Invest in Innovation Kaizen
• Take CAPA
• Define QMS
▪ Talk the Business Language
▪ Never talk about non-compliance, talk only ‘Business Risks’
▪ Make Delivery Teams own the Process
▪ Have a Team that shares your Dreams
▪ Communicate effectively at all levels
▪ Believe & Invest in Innovation