Ravi is an IT consultant with over 30 years of experience in the industry. He has helped global organizations in the US, UK, Australia, China, Singapore and Malaysia - in designing and implementing Quality and Process Improvement initiatives involving Agile and traditional methodologies. He has a strong software development background and practical experience in project management. He developed a 90-Day program to jump start an IT organization into the Agile / DevOps Adoption Journey. He also architected the flagship solution – the IT process repository – of the consulting practice at Infosys. He has coached multiple programs in client organizations as part of their enterprise Agile transformation. Ravi has a passion to write and present his thoughts and has published 40+ papers / articles / blogs in Research Journals and Web Communities and has presented in many Agile-DevOps conferences.

Don’t implement SRE like this!

Site Reliability Engineering (SRE) is a discipline that helps IT organizations create scalable and reliable software systems to deliver business value faster. SRE enables this by balancing development of new features and running production systems smoothly and reliably. SRE originated at Google and many IT organizations have implemented this in many different ways.

IT organizations have the liberty to contextualize SRE for their own solution development and operation functions. However if the basic principles and practices are not used as the foundation SRE implementation will only be for the sake of it without business benefits. In fact the teams may feel constrained if they are forced to adopt certain practices under the guise of SRE.

This presentation identifies the anti-patterns of SRE implementation and indicates how Kanban principles could be used to best utilize the error budgets.