Is DevOps bigger than Agile? What the future holds. Jenkins World. #JenkinsWorld

Transcription

1 Is DevOps bigger than Agile? What the future holds Jenkins World #JenkinsWorld

2 Zubin Irani, CEO cprime Zubin s background includes a Bachelor Degree from USC, and a MBA from Columbia & Berkeley. # # cprime is a leader in Enterprise Agile Transformations and Software services focused on Agile, ALM and DevOps.# # cprime has been ranked Top 50 fastest growing companies in Silicon Valley for the last 6 consecutive years. Clients include: Largest Social Networking Company Largest Credit Card Company Largest Technology Company Largest Search Engine Company Largest Financial Company Largest Entertainment Company

3 Over X% of the Agile Community believes DevOps is critical to Agile Success Over Y% of the Agile Community has limited knowledge of DevOps? *Survey of 850+ Scrum Alliance Members

4 Over 55% of the Agile Community believes DevOps is critical to Agile Success Over 80% of the Agile Community has limited knowledge of DevOps? *Survey of 850+ Scrum Alliance Members

5 Who s in the Audience today?

6 Agile cannot survive without DevOps DevOps is meaningless without Agile

7 Objectives An explanation of why DevOps is important to Agile Key s to a successful DevOps Transformation The relationship between Agile & DevOps

8 Descriptors of DevOps 1. Continuous Integration (CI): A process in which developers and testers validate new code. 2. Continuous Delivery (CD): The process of creating releasable artifacts. 3. Dynamic Cloud infrastructure: The virtualization of infrastructure that optimizes computing resources. 4. Test Automation: The scripts that carry out both functional and interface testing. 5. Security Automation: The scripts that carry out security checks, increasingly known as DevSecOps 6. Monitoring: Constant measurement of the environment to proactively address issues

9 Agile, a brief history Agile was a grassroots movement for the first 10 years # (out of 15) Only recently (last 3-5 years) has Agile has gone mainstream 5 Driving factors for crossing the chasm 1. Inertia from grassroots efforts 2. Business found a way to work around IT 3. The pace of global competition exponentially increased 4. Scaling solutions went mainstream 5. Top Talent and new hires demand

10 Agile, what went well Timing; People (Developers, Testers, Project Managers) were ready for change Years of repetitive failures and sacrificed nights & weekends Impossible deadlines set up projects to fail before they started A rebellion was just waiting for a leader to show them the way# Momentum; A coordinated movement with a good definition, and a smart business plan A central body that defined a common standard & language A well marketed certification test to a community that values it A well sized group of consultants who became certified Trainers and evangelists, spread the word of Agile like wildfire

11 Agile, what didn t go well Agile Coaching Allergic to technology Low barriers to entry The result: Coaching shifted towards easier problems to solve (team only focus, professional facilitators very far away from code) Lacks stickiness Fractured Communities Coaching communities have aligned along tribal lines and become fragmented and argumentative; Scrum Alliance vs Scrum.org vs. SAFe Lack of Innovative Thinking

12 Agile Transformations; Success Patterns A Pain or burning desire for change, end goal is clear, with a clear roadmap Executive engagement, knowledge & support Money + Time must be funded to support Process + Tool changes (Millions of dollars) A cross cutting initiative that tackles Process and Technology together

13 We believe the industry needs a unified software services framework that supports the connected world of software delivery Software Services Lifecycle Management (SSLM) addresses the fragmented way software AND services are used in support of Agile, DevOps and ALM initiatives.

14 Over 55% of the Agile Community believes DevOps is critical to Agile Success Over 80% of the Agile Community has limited knowledge of DevOps? *Survey of 850+ Scrum Alliance Members

15 How to become a DevOps Champion 1. Through Automation you can get the right features delivered with high-quality 2. Learn how to speak Agile 3. What s important to your organization is not necessarily what s important to you Performance management, Scalability, Configuration Management, etc while important, aren t primary value drivers for Agilists

16 Key Takeaways Go Get the funding you need Focus on Educating Just say No to Silos Work with PMO, Product Management, Agile Leaders when designing and developing your architecture to insure their tools align well in the pipeline. Designate a Central Champion to act as the Enterprise Change Agent owning both the technology and the process initiative DevOps cuts across the whole organization Build consensus around business benefits with Executives, ROI

17 Agile & DevOps Predictions 1. Convergence is an absolute certainty. The question remains who will be in the drivers seat? 2. DevOps will be twice as big as Agile 3. Agile coaches will need to adapt or die Risks: DevOps community needs to avoid the pitfalls of tribalism

18 Thank linkedin.com/in/zubin