© Verizon 2017, All Rights Reserved. Information contained herein is provided AS IS and subject to change without notice. All trademarks used herein are property of their respective owners. Where DevOps Runs Head On Against Corporate Culture Mohamad Bayan The icons for this presentation were made available from www.flaticon.com

© Verizon 2017, All Rights Reserved. Information contained herein is provided AS IS and subject to change without notice. All trademarks used herein are property of their respective owners. 2 Digital Transformation Process People Technology

© Verizon 2017, All Rights Reserved. Information contained herein is provided AS IS and subject to change without notice. All trademarks used herein are property of their respective owners. 3 Digital Transformation Process People Technology Cloud Computing Big Data APIs Product Team Agile DevOps Omni-channel Innovation Social Media Mobile First Design Thinking IoT Empathize Define Ideate Prototype Test

© Verizon 2017, All Rights Reserved. Information contained herein is provided AS IS and subject to change without notice. All trademarks used herein are property of their respective owners. CAMS describes the core values of the DevOps Movement - John Willis and Damon Edwards 4 DevOps Components Automation Culture Measurement Sharing

© Verizon 2017, All Rights Reserved. Information contained herein is provided AS IS and subject to change without notice. All trademarks used herein are property of their respective owners. CAMS describes the core values of the DevOps Movement - John Willis and Damon Edwards 5 DevOps Components Automation Culture Measurement Sharing Easier Harder

© Verizon 2017, All Rights Reserved. Information contained herein is provided AS IS and subject to change without notice. All trademarks used herein are property of their respective owners. • Even with the best tools, DevOps is just another buzzword if you don't have the right culture. • Changing an organization's culture is one of the most difficult leadership challenges. 6 Culture is hard to change

© Verizon 2017, All Rights Reserved. Information contained herein is provided AS IS and subject to change without notice. All trademarks used herein are property of their respective owners. • Separate (Permanent) Team • Tooling • Automation 7 Anti-Pattern: DevOps Topology within Corporates Dev Ops DevOps DevOps Topologies and Anti-Types: http://web.devopstopologies.com/

© Verizon 2017, All Rights Reserved. Information contained herein is provided AS IS and subject to change without notice. All trademarks used herein are property of their respective owners. • Separate (Permanent) Team • Tooling • Automation 8 Anti-Pattern: DevOps Topology within Corporates Dev Ops DevOps Building another silo keeps Dev and Ops further apart and doesn’t address the culture. DevOps Topologies and Anti-Types: http://web.devopstopologies.com/

© Verizon 2017, All Rights Reserved. Information contained herein is provided AS IS and subject to change without notice. All trademarks used herein are property of their respective owners. Its alright if it’s: • A Temporary Team with the goal of bringing Dev and Ops closer together. • An ongoing Evangelists Team that helps spread awareness of DevOps practices. 9 Anti-Pattern: DevOps Topology within Corporates Dev Ops DevOps DevOps Topologies and Anti-Types: http://web.devopstopologies.com/

© Verizon 2017, All Rights Reserved. Information contained herein is provided AS IS and subject to change without notice. All trademarks used herein are property of their respective owners. • What does your corporate culture look like? • How does your culture and the way you work support DevOps? 10 DevOps Culture

© Verizon 2017, All Rights Reserved. Information contained herein is provided AS IS and subject to change without notice. All trademarks used herein are property of their respective owners. • What does your DevOps topology look like? • Do you still have silos between development and operations? • How many tickets do you have to create to deliver code to production? • How many handoffs does a deliverable go through to make it to production? 11 Organizational Silos DevOps Topologies and Anti-Types: http://web.devopstopologies.com/ Dev Ops

© Verizon 2017, All Rights Reserved. Information contained herein is provided AS IS and subject to change without notice. All trademarks used herein are property of their respective owners. • Do Dev and Ops share the same goals of focusing on quality and customer? • Do Dev and Ops still have different incentives/objectives?  Code Delivered: Features and Deadlines  Up-Time: Stability and Production availability 12 Mutual Goals Change Stability

© Verizon 2017, All Rights Reserved. Information contained herein is provided AS IS and subject to change without notice. All trademarks used herein are property of their respective owners. DevOps thrives on experimentation and continuous improvement opportunities. • Does your culture encourage and support experimentation? • Do you feel shy or nervous to try anything new? • Is Innovation limited to a certain groups? 13 Open to Experimentation

© Verizon 2017, All Rights Reserved. Information contained herein is provided AS IS and subject to change without notice. All trademarks used herein are property of their respective owners. With continual experimentation, failures will happen. • How does your culture handle failures? • Does it embrace failure? • Does your culture encourage “fail fast, fail forward” mentality? 14 Failure

© Verizon 2017, All Rights Reserved. Information contained herein is provided AS IS and subject to change without notice. All trademarks used herein are property of their respective owners. • Do you have the proper feedback loops between Dev and Ops? • Do you have communication channels established across teams within the organization? 15 Communication and Feedback Loops

© Verizon 2017, All Rights Reserved. Information contained herein is provided AS IS and subject to change without notice. All trademarks used herein are property of their respective owners. • Do all teams and individuals throughout the organization collaborate and share knowledge as needed? • Are the teams territorial and work in silos? • Do you have to go through management in order to collaborate with other team members? 16 Collaboration and Knowledge Sharing

© Verizon 2017, All Rights Reserved. Information contained herein is provided AS IS and subject to change without notice. All trademarks used herein are property of their respective owners. • Do team members feel safe to speak up and to take risks? • De team members feel accepted and respected? • Do all teams truly work toward achieving a common business goal? 17 Psychological Safety

© Verizon 2017, All Rights Reserved. Information contained herein is provided AS IS and subject to change without notice. All trademarks used herein are property of their respective owners. • Do you feel there are synergy and trust between your team members? • Do you trust other teams are operating with the organization’s best interest at heart? • Do you trust your leadership to provide the right support as you experiment and fail? 18 Trust

© Verizon 2017, All Rights Reserved. Information contained herein is provided AS IS and subject to change without notice. All trademarks used herein are property of their respective owners. 19 DevOps Culture & Maslow’s hierarchy of Needs • Organizational Silos • Mutual Goals • Open to experimentation • Failure • Psychological Safety • Communication and Feedback Loops • Collaboration and Knowledge Sharing. • Trust Self- actualization Full Potential including creative activities Physiological Food, Water, Warmth, Rest Safety Security, Safety Belongingness and Love Relationships, Friends Esteem Feeling of Accomplishment

© Verizon 2017, All Rights Reserved. Information contained herein is provided AS IS and subject to change without notice. All trademarks used herein are property of their respective owners. 20 DevOps Culture & Maslow’s hierarchy of Needs • Organizational Silos • Mutual Goals • Open to experimentation • Failure • Psychological Safety • Communication and Feedback Loops • Collaboration and Knowledge Sharing. • Trust Self- actualization Full Potential including creative activities Physiological Food, Water, Warmth, Rest Safety Security, Safety Belongingness and Love Relationships, Friends Esteem Feeling of Accomplishment