9 dev ops mark smalley & lex scholten - when and how to devops

15
When and how to DevOps Mark Smalley, ASL BiSL Founda>on Lex Scholten, Mo>vaty 1

Upload: nmitsymposium

Post on 10-Aug-2015

113 views

Category:

Technology


0 download

TRANSCRIPT

Page 1: 9 dev ops   mark smalley & lex scholten - when and how to devops

When  and  how    to  DevOps  

Mark  Smalley,  ASL  BiSL  Founda>on  Lex  Scholten,  Mo>vaty  

  1  

Page 2: 9 dev ops   mark smalley & lex scholten - when and how to devops

Mark  

• DevOps  

• Benefits  • Capabilities  • Preconditions  

 Agenda  

Lex  

• Interventions  •  Team  behavior  •  Leadership  style  •  Paradigm  shift    

•  Summary    

2  

Page 3: 9 dev ops   mark smalley & lex scholten - when and how to devops

Movement  Philosophy  Community  

Collaboration  Multidisciplinary  Dev  +  Ops  +  …  

Resilience  

Culture  Automation  

Lean  Metrics  Sharing  

 What  is  DevOps?  

3  

Page 4: 9 dev ops   mark smalley & lex scholten - when and how to devops

 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  

Page 5: 9 dev ops   mark smalley & lex scholten - when and how to devops

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  

Page 6: 9 dev ops   mark smalley & lex scholten - when and how to devops

Which  capabilities  do  I  need    if  I  want  to  do  DevOps?  

Illustration:  blog.devopsguys.com   6  

Page 7: 9 dev ops   mark smalley & lex scholten - when and how to devops

 Culture  is  key  –  but  difficult  

Illustration:  blog.devopsguys.com   7  

Page 8: 9 dev ops   mark smalley & lex scholten - when and how to devops

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  

Page 9: 9 dev ops   mark smalley & lex scholten - when and how to devops

• 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  

Page 10: 9 dev ops   mark smalley & lex scholten - when and how to devops

• 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  

Page 11: 9 dev ops   mark smalley & lex scholten - when and how to devops

Change  of  Team  behavior  

Change  of  Leadership  style  

Paradigm  shiQ  

These  are  the  kind  of  interventions    that  you  should  consider  

11  

Page 12: 9 dev ops   mark smalley & lex scholten - when and how to devops

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  

Page 13: 9 dev ops   mark smalley & lex scholten - when and how to devops

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  

Page 14: 9 dev ops   mark smalley & lex scholten - when and how to devops

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  

Page 15: 9 dev ops   mark smalley & lex scholten - when and how to devops

•  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