9 dev ops mark smalley & lex scholten - when and how to devops
TRANSCRIPT
When and how to DevOps
Mark Smalley, ASL BiSL Founda>on Lex Scholten, Mo>vaty
1
Mark
• DevOps
• Benefits • Capabilities • Preconditions
Agenda
Lex
• Interventions • Team behavior • Leadership style • Paradigm shift
• Summary
2
Movement Philosophy Community
Collaboration Multidisciplinary Dev + Ops + …
Resilience
Culture Automation
Lean Metrics Sharing
What is DevOps?
3
Identify Mgmt AD/AM
Users ITSM
Benefit
Use
Demand
Supply
Consume
Provide
Evaluate
Apply
Specify
Develop
Deploy
Run
Support
Info Syst Dev Ops Lite
DevOps has a broader scope but we’re focusing on deployment benefits
4
How does the business benefit from improvements to deployment?
• Quicker,
• more reliable and
• cheaper deployment of new software releases
• speeds up IT-‐related business change (more, better, different business) and
• reduces business costs and risks
5
Which capabilities do I need if I want to do DevOps?
Illustration: blog.devopsguys.com 6
Culture is key – but difficult
Illustration: blog.devopsguys.com 7
Executive “This DevOps stuff sounds good”
Consultant “Your current CALMS score is low”
Executive: “So what do I need to improve it and get the benefits?”
Illustration: www.rackspace.com
So you want DevOps too?
8
• Need more benefits than just cost reduction
• Are prepared for fundamental cultural change
• Have practitioners who want to pioneer
• Reward bottom-‐up experiments
• Drive synergies between business divisions
You can reap the benefits from DevOps when you
9
• Need more benefits than just cost reduction
• Are prepared for fundamental cultural change
• Have practitioners who want to pioneer
• Reward bottom-‐up experiments
• Drive synergies between business divisions
You can reap the benefits from DevOps when you
10
Change of Team behavior
Change of Leadership style
Paradigm shiQ
These are the kind of interventions that you should consider
11
Old behavior New behavior Desired effect Focus on team size Right person for the right job
Focus on results Stable rather than fixed
Focus on result Added value
Wait for orders Constraints rather than rules Team mission
Ownership/commitment
Judge by mistakes Reward the right behavior
Promote experiments S>mulate improvements
Compe>>on = defend your own territory
Compe>>on between teams – consider gamifica>on Fun!
Promote experiments S>mulate improvements
Team behavior
12
Old behavior New behavior Desired effect Manage from behind your desk
Start with why -‐ context Goals rather than tasks What rather than how Constraints rather than rules Walk around / ask why Team mission
Ownership/commitment
Judge by mistakes Mistakes are OK Use mistakes to learn Be honest about the complexity of things Reward the right behavior
Promote experiments S>mulate improvements
“Let me show you how” Hands behind your back Improve by example Focus on results
Ownership/commitment Deliver what is needed Add value
Postpone decisions Dare to take decisions Focus on what is needed Ownership
Leadership style
13
Old behavior New behavior Desired effect Control by limi>ng freedom
Control used for feedback Con>nuous improvement Learning Mo>va>on
Blame people Cover your back
Address desired behavior Improve coopera>on Coopera>on to reach results
Metrics to report Metrics to improve Con>nuous improvement Learning
Provide direc>on Provide correc>on Con>nuous improvement Learning
Focus on Projects Focus on Opera>ons Add value It’s your fault How can I help you? Think as a team
Paradigm shift
14
• DevOps is a multidisciplinary movement
• Speeds up IT-‐related business change and reduces business costs and risks
• Entails fundamental cultural change
• Looser leadership style • Self-‐organizing teams • Paradigm shift towards experimentation, learning, continuous improvement, teamwork
Summary
15