Ravi Tadwalkar as SM/DevOps/management/Coach
•
1 like•688 views
The document discusses the roles and responsibilities of a Scrum Master, DevOps Manager, and DevOps Coach. It provides examples of how DevOps adoption improved deployment processes at companies like PayPal and Western Digital. Specifically, implementing continuous integration/deployment and embedding release engineers into agile teams reduced PayPal's deployment time from 6 weeks to 9 days. For Western Digital, using a common code repository improved their firmware integration from twice a week to on-demand. The document also outlines the author's experience over 20 years in software development, management, coaching, and DevOps roles.
Report
Share
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (8)
Similar to Ravi Tadwalkar as SM/DevOps/management/Coach
Similar to Ravi Tadwalkar as SM/DevOps/management/Coach (20)
More from Ravi Tadwalkar
More from Ravi Tadwalkar (19)
Recently uploaded
Recently uploaded (20)
Ravi Tadwalkar as SM/DevOps/management/Coach
- 1. - Ravi Tadwalkar - SM (Scrum Master), DevOps Manager/Coach Role
- 2. SM, DevOps Manager/Coach Roles and Responsibilities • Pertinent DevOps Adoption Examples • Relevant Roles and Responsibilities as Dev Manager, SM and DevOps Coach
- 3. Pertinent DevOps Adoption Examples • Lack of DevOps meant “potentially” shippable…forever • Example of PayPal Data Technology group • Problem: 4 hours of ETL development took 6 weeks to deploy even at PayPal! • Solution: better deployment pipeline for big data & SQL DBs • Process: VSM & 5-whys as tools to identify constraints, embrace “system as a whole” • Execution: embed release engineer in each agile team, to pilot CI w/ automated unit tests and acceptance tests with single-click deploys • Result: average lead time reduced from 6 weeks to 9 days! • Lack of DevOps meant “doing” agile, not “being” agile • Example of Western Digital’s NAS Content Solutions Group • Problem: firmware integration blues between middleware API team & ODM vendor • Solution: common GIT repo for integrated deployment pipeline • Process: embrace “System as a whole” rather than local optimization at team-level CI projects for multiple deployment pipelines • Execution: implemented ODM vendor team Kanban for “just in time” firmware builds • Result: Frequency of CI builds improved from “twice a week” to on-demand integration for upcoming continuous deployment pipeline! • Before DevOps adoption, DEV & OPS collaborated:
- 4. Experience as Dev Manager, SM and DevOps Coach During 4 of last 7 years, I have been coaching agile teams on software craftsmanship, DevOps & Release Engineering: • Release Manager • 2 years at Symantec (Experience Report) • SM & DevOps Coach • 1.5 years at PayPal, leading kanban & CI adoption • 2 years at Cisco, evangelizing on software craftsmanship • Agile Coach • Last 11 months with WDC, leading agile adoption During 8 years prior to that, I was in a startup: • Dev Manager • Hands-on servant leader initiating technical work w/ UML models • Leading engineers w/ drive: autonomy->mastery->purpose • Mentoring engineers on software engineering standards During 4 years during Dot Com era, hands-on dev: • Software Developer & Architect • Created & implemented UML models for CP ships • Created UML models for NASA’s experimental payload system • Contributed to C++ framework behind promotion engine
Editor's Notes
- 15 minute presentation illustrating my past work experience, Roles & Responsibilities; and how would I fit well into SM (Scrum Master) / DevOps Manager/Coach Role. Source attribution for note below: http://www.agilealliance.org/resources/learning-center/what-devops What is Devops? This is the second most asked question today in IT. Obviously behind “What is a Cloud?”. Most people who have been following the Devops movement for the past three years would agree it really doesn’t or maybe shouldn’t even have a definition. For example “What is Agile?” doesn’t really have a simple answer. A general consensus of like minded Devops followers might agree with Adam Jacob’s, (founder of Opscode), definition of “It’s a cultural and professional movement”. That’s it. However, in this session we are going to try and expand on the ideas behind the Devops movement. We will attempt to discuss the “Why” of Devops. Why does it exist, what is it’s history, what are some of it’s patterns and also look at some practitioning examples. We will start by looking at some of the roots of the movement breaking down it’s history. We will take a deeper look at the following influences: * Lean Manufacturing * Lean Startup * Agile and Agile Infrastructure * Continuous Delivery * Web Scale We will look at some of the direct and indirect influences of twentieth century management scientist like Deming, Goldratt and Ohno. We will also will look at taxonomy that has been used to try and identify certain patterns of Devops called CAMS. * Culture * Automation * Measurement * Sharing And finally we will end up with a look at some successful Devops style companies who have been capturing the mindshare of this movement. Companies like: * Etsy * Github * Netflix
- 2 slides illustrating my relevant work experience, Roles & Responsibilities; and 2 recent examples of pertinent experience in working with DevOps. Hopefully, this will illustrate how would I fit well into SM (Scrum Master) / DevOps Manager/Coach Role.
- In this slide, I have 2 recent examples of my pertinent experience in working with DevOps. Hopefully, this will exemplify how well I would fit into SM (Scrum Master) / DevOps Manager/Coach Role.
- This slide is about my relevant work experience, illustrating that I have grown through progressive ranks as Software Developer, Enterprise Architect, Dev Manager, and most recently SM/Coach and Evangelist. Each Role is listed with my work experience, with primary responsibility/contribution. You will notice recent examples of pertinent 4+ years experience in working with DevOps. Hopefully, this will illustrate how would I fit well into SM (Scrum Master) / DevOps Manager Role.