SlideShare a Scribd company logo
a devops
                                                          mentality


                                         @patrickdebois

http://spencerfry.com/how-to-bootstrap
Thank you!
devops

      Cultural and
 Professional Movement


http://www.youtube.com/watch?v=Fx8OBeNmaWw   Adam Jacob
My Background
• Independent consultant
• Have worked in different roles
• Agile and Infrastructure
• Just Enough Developed Infrastructure - http://jedi.be
• Started organizing devopsdays
• Recently joined Cutter Consortium
Background check?
analysts     database
developer    security
operations   middleware
testers      sales
network      manager
storage      hr people
The movement is inclusive

            Awesome
             Happy
               Cool
         Built neat stuff!



                             Adam Jacob
Bootstrapping a-devops-matter
There are exclusive people

                Grumpy
              Tool Centric
              Us vs Them
      I’m a devop you’re a sysadmin



                                      Adam Jacob
Looking for tools?
Looking for tools?


You can still leave ...
DEV         OPS



    The
  problem
“It’s NOT a technical
       problem”
“It’s a human
    problem”
We don’t trust                We don’t trust
 the guys from                 the guys from
  operations.                  development.
   They suck                     They suck

                 We don’t trust
                  the guys from
                  management.
                    They suck
Premise today
“It’s a trust problem”
Starting a devops
    culture =
 restoring trust




             http://voetstappen.blogspot.com/
Bootstrapping a-devops-matter
Traditional Business Formula


(Strategy X Execution)
= Results
Factor
(Strategy X Execution)
* Trust = Results
of
             Trust




(-) Trust = (-) Speed (+) Cost
(+) Trust =(+) Speed!(-) Cost!
Tax Dividend


• 10 x 10 = 100 (- Tax 40 %) = 60
• 10 x 10 = 100 (- Tax 10 %) = 90
• 10 x 10 = 100 (+ Div 20%) = 120
Trust = f(character, competence)
Waves of Trust
       Self
   Relationship
  Organizational
     Market
     Societal
1. Self Trust
“We trust people,
who make things happen”
But ...
Can others
trust you?
“We judge others by their behavior,
we judge ourselves by our intentions”
Principle of Credibility
    “The 4 Cores”
• Trust = f(character, competence)
• Character = f(integrity, intent)
• Competence = f(capabilities, results)
Capability
Talents
Attitudes
Skills
Knowledge
Style
Ah, so this is where the
 (cool)tools come in !
Chef         Ruby     Mysql        Linux
Puppet       Java     Redis       Mac OSX


 Event
                                     EC2
Machine
Node.js   I <3 technology           Vmware


  Fog        Nginx    Vagrant       Sinatra
Jclouds      Thin    Virtualbox      Rails
Craftsmanship
Technology       Management

But there’s a *lot* more
Social               Financial

         Communication
WTF, do I need to
 learn all that?
Broader knowledge,
will make your actions
   more balanced
It’s NOT about devs
taking over ops or ops
    taking over devs.
It’s about
   collaboration
with people you trust.
Results:

• Take responsibility for results not just your
  action. Avoid , my job is only to ...
• Expect to finish the job
• Finish strong
Bootstrapping
Make a personal backlog
• Plan an item you can really make happen
 • No too big, make it feasible
• (Result)Define what you want to achieve
• (Competence)Learn what you need
• Do : trust comes if you make things happen
• Check the result
• Act on it
As a person

• I want to develop these capabilities
• I want to achieve results
• When I fail , I want to learn and improve!
As a manager, I want to
   • help people develop these capabilities
   • help people achieve results
      • (support the people)
   • help people fail and learn and improve!

(+) Trust =(+) Speed!(-) Cost!
2. Relational Trust
Reach out to others
Agile already did a great job
Get
     together
             find allies
           forward links
         organize meetups
         distribute books
   find people with real issues
kindly ignore nay sayers (for now)
You can use technology
      to get the
conversation started
• Continuous Delivery   • Testing, Monitoring
• Automation            • Fixing a problem
• Scalability           • Infrastructure as code
• Performance           • <whatever>
“Seek to establish trust”
    Technology Trust by Testing, Monitoring
          Human Trust by Behavior
13 Behaviors
 “trust is established through action”

• Needs to be            • Sweet Spot
  balanced                  (Strength)
• Too Little             • Too much
  (Weakness)                (Weakness)



• f.i. talk straight vs demonstrate respect
#1 Talk Straight
 • We really need this tool vs I want to
   learn this tool
 • It needs to be finished by X (that
   leaves me some time)
 • The user/my boss wants this now
 • It’s urgent, it’s important
#2 Demonstrate Respect
  • we judge a person’s character, by how he
    treats people who can’t help or hurt him
  • little things , making things helpful
#3 Create Transparency
• no more Bob’s directory
• check in your code
• expose logfiles, config files ...
• visualize progress (Kanban, Burndown)
• share your information
• make results repeatable
#4 Right wrongs
“to know what is right and not to
do it is the worst cowardice” - Confucius



 • when you know there is a short cut, fix it
   and don’t leave it
 • fix a bug when it occurs, write a test
 • fix it, fix it all the way
#5 Show loyalty

        • give credits
        • talk as if people were
          present
        • represent others
#6 Deliver Results
• Clarify Results upfront
 • your definition vs my definition
• Small steps = Validation test (Userstories)
#7 Get Better
       “Illiterate are those who can not
  learn, unlearn, relearn” - Alvin Toffler

• seek feedback (Retrospectives)
• learn from mistakes (5 whys)
• ask: what to continue, what to stop, what to
  start now!
• metrics (Neutral , not emotional)
• change the system (Systems Thinking)
#8 Confront Reality



• avoid 99% finished
• burn down chart
• only measure of progress is working
  software (in production)
#9 Clarify Expectations

  • deadlines vs. cut corners (win-win or no
    deal), negotiate them (who vs trust)
  • talk to devs, what do they expect
  • talk to admins, what do they expect
  • talk to customers
#10 Practice Accountability

 • Accountability requires facing Truth
 • yourself and others
 • Don’t blame others , no pointing fingers
#11 Listen First
“If there is any secret, it lies in the ability
to put yourself in the other person’s place”
                 - Henry Ford
#12 Keep Commitments

• don’t PR your way out
• make them careful
• group is committed to results (not manager)
• mgt supports team to keeping commitments
#13 Extend Trust
             • Make it an action
              • here is the password
              • here is the code
              • everybody can check in and
                 deployed to prod (with tests :)

remember it’s inclusive not exclusive!
As a person,

• Given my capabilities
• I want to practice these 13 behaviors
• Help others to practice these 13 behaviors
As a manager, I want to

   encourage behavior that increases trust




(+) Trust =(+) Speed!(-) Cost!
“Don’t change culture,
  change behavior!”
Organizational Trust
                   Eli
                         mi
                              na
•   Redundancy                  te
                                     Ta
                                       xe
•   Bureaucracy                           s
•   Politics

•   Disengagements (quit and stay)

•   Turnover (employee)

•   Churn (stakeholders)

•   Fraud
Interesting Books
Want to know more?



  #devops on twitter & irc
    http://devopsdays.org
    http://devopscafe.org
   http://planetdevops.net
    devops googlegroup
devops-toolchain googlegroup
QUESTIONS?
Thank you!




Patrick Debois - http://jedi.be/blog - @patrickdebois

More Related Content

PDF
12 Take Aways - Managing the Unmanageable
PPT
12 Take Aways - Managing the Unmanageable
PPTX
AgileCamp 2014 Track 5: The Seven Wastes - Can You Get Leaner
PDF
Managing Using Intuition and Rules of Thumb 050113
PPT
Money, Process, and Culture- Tech 20/20 June, 2012
PPT
Crash Course: Managing Software People and Teams (IEEE, 4.4.13)
PDF
Steal from the best
PDF
12 take aways - managing the unmanageable
12 Take Aways - Managing the Unmanageable
12 Take Aways - Managing the Unmanageable
AgileCamp 2014 Track 5: The Seven Wastes - Can You Get Leaner
Managing Using Intuition and Rules of Thumb 050113
Money, Process, and Culture- Tech 20/20 June, 2012
Crash Course: Managing Software People and Teams (IEEE, 4.4.13)
Steal from the best
12 take aways - managing the unmanageable

What's hot (20)

PPTX
Pellissippi State AITP Meeting November 2014
PDF
Building and Growing an Agile Team
PDF
On the Startup Team
PDF
Becoming an Agile Manager (bay scrum, 10.24.13)
PDF
Do you want to be a manager (are you sure)
PDF
AIPMM talk - chaos to clarity: managing the unmanageable, ron lichty, 12.7.12
PPTX
Thinking Through A Cybermissions Project - a presentation to get your team mo...
PDF
If We Are Agile, Why Do We Need Managers? (AgileIndy, 5.14)
PPTX
Agile Leadership 201: Enriching Management
PPTX
Marty Weiner, Reddit CTO @ SXSWi 2016 - Everything's Harder At Scale
PPTX
Answer Is Irrelevant: Leadership In A Changed World
PDF
Startupfest 2016: MARTY WEINER (Reddit) - How to
PDF
Agile Is Hard (AgileCampSV 2014)
PDF
Scrum: From the Classroom to the Workplace :: FCUP 2018
PPT
Transforming chaos to clarity - acm 6.15
PPTX
Peoplware slides tech session
PPTX
Work itout presentation
PDF
Teamwork - making your dream team come true
PPTX
What is devops
Pellissippi State AITP Meeting November 2014
Building and Growing an Agile Team
On the Startup Team
Becoming an Agile Manager (bay scrum, 10.24.13)
Do you want to be a manager (are you sure)
AIPMM talk - chaos to clarity: managing the unmanageable, ron lichty, 12.7.12
Thinking Through A Cybermissions Project - a presentation to get your team mo...
If We Are Agile, Why Do We Need Managers? (AgileIndy, 5.14)
Agile Leadership 201: Enriching Management
Marty Weiner, Reddit CTO @ SXSWi 2016 - Everything's Harder At Scale
Answer Is Irrelevant: Leadership In A Changed World
Startupfest 2016: MARTY WEINER (Reddit) - How to
Agile Is Hard (AgileCampSV 2014)
Scrum: From the Classroom to the Workplace :: FCUP 2018
Transforming chaos to clarity - acm 6.15
Peoplware slides tech session
Work itout presentation
Teamwork - making your dream team come true
What is devops
Ad

Viewers also liked (9)

PDF
Morango cms
PPT
Mongo db and_academia
PDF
Hive at Last.fm
PDF
Arun Gupta: London Java Community: Java EE 6 and GlassFish 3
PPT
I went to_a_communications_workshop_and_they_t
PPTX
Dmitry mozorov on code quotations code as-data for f#
PPTX
Push newchallenges
PDF
A poet's guide_to_acceptance_testing
PPTX
Greg Young on Architectural Innovation: Eventing, Event Sourcing
Morango cms
Mongo db and_academia
Hive at Last.fm
Arun Gupta: London Java Community: Java EE 6 and GlassFish 3
I went to_a_communications_workshop_and_they_t
Dmitry mozorov on code quotations code as-data for f#
Push newchallenges
A poet's guide_to_acceptance_testing
Greg Young on Architectural Innovation: Eventing, Event Sourcing
Ad

Similar to Bootstrapping a-devops-matter (20)

PPTX
How Yammer Stayed Lean Post-Acquisition: Customer Development as Survival Str...
PDF
A tale of two startups
PDF
Mokita training
PDF
Kellogg VC CEO Summit
PPT
Agile for Me- CodeStock 2009
PDF
DevOps Picc12 Management Talk
PDF
Software development management slides by George Berkowski (Hailo)
KEY
10 Observations from 10+ years in the Corporate UX Trenches
PDF
Measuring Team Happiness – A Real-Life Journey of Fostering an Engaging Worki...
PPTX
Letting the cards speak: Agile planning for SharePoint
PDF
devops - what's missing? what's next?
KEY
The human side of design
PDF
No Governance as Usual
PDF
Design Operations
PDF
Building Resilience: Practical Tools for Keeping Your Head While Navigating a...
PDF
Destroying DevOps Culture Anti-Patterns
PPTX
Selling UX
PDF
You Cant Be Agile If Your Code Sucks (with 9 Tips For Dev Teams)
PDF
Leading Without Seeing: managing distributed teams
PPTX
Rock the tech interview january 2015
How Yammer Stayed Lean Post-Acquisition: Customer Development as Survival Str...
A tale of two startups
Mokita training
Kellogg VC CEO Summit
Agile for Me- CodeStock 2009
DevOps Picc12 Management Talk
Software development management slides by George Berkowski (Hailo)
10 Observations from 10+ years in the Corporate UX Trenches
Measuring Team Happiness – A Real-Life Journey of Fostering an Engaging Worki...
Letting the cards speak: Agile planning for SharePoint
devops - what's missing? what's next?
The human side of design
No Governance as Usual
Design Operations
Building Resilience: Practical Tools for Keeping Your Head While Navigating a...
Destroying DevOps Culture Anti-Patterns
Selling UX
You Cant Be Agile If Your Code Sucks (with 9 Tips For Dev Teams)
Leading Without Seeing: managing distributed teams
Rock the tech interview january 2015

More from Skills Matter (20)

PDF
5 things cucumber is bad at by Richard Lawrence
ODP
Patterns for slick database applications
PDF
Scala e xchange 2013 haoyi li on metascala a tiny diy jvm
ODP
Oscar reiken jr on our success at manheim
ODP
Progressive f# tutorials nyc dmitry mozorov & jack pappas on code quotations ...
PDF
Cukeup nyc ian dees on elixir, erlang, and cucumberl
PDF
Cukeup nyc peter bell on getting started with cucumber.js
PDF
Agile testing & bdd e xchange nyc 2013 jeffrey davidson & lav pathak & sam ho...
ODP
Progressive f# tutorials nyc rachel reese & phil trelford on try f# from zero...
ODP
Progressive f# tutorials nyc don syme on keynote f# in the open source world
PDF
Agile testing & bdd e xchange nyc 2013 gojko adzic on bond villain guide to s...
PDF
Russ miles-cloudfoundry-deep-dive
KEY
Serendipity-neo4j
PDF
Simon Peyton Jones: Managing parallelism
PDF
Plug 20110217
PDF
Lug presentation
PDF
Plug saiku
PDF
Huguk lily
PDF
Personal kanban-workshop
PDF
Agilex retrospectives
5 things cucumber is bad at by Richard Lawrence
Patterns for slick database applications
Scala e xchange 2013 haoyi li on metascala a tiny diy jvm
Oscar reiken jr on our success at manheim
Progressive f# tutorials nyc dmitry mozorov & jack pappas on code quotations ...
Cukeup nyc ian dees on elixir, erlang, and cucumberl
Cukeup nyc peter bell on getting started with cucumber.js
Agile testing & bdd e xchange nyc 2013 jeffrey davidson & lav pathak & sam ho...
Progressive f# tutorials nyc rachel reese & phil trelford on try f# from zero...
Progressive f# tutorials nyc don syme on keynote f# in the open source world
Agile testing & bdd e xchange nyc 2013 gojko adzic on bond villain guide to s...
Russ miles-cloudfoundry-deep-dive
Serendipity-neo4j
Simon Peyton Jones: Managing parallelism
Plug 20110217
Lug presentation
Plug saiku
Huguk lily
Personal kanban-workshop
Agilex retrospectives

Bootstrapping a-devops-matter

  • 1. a devops mentality @patrickdebois http://spencerfry.com/how-to-bootstrap
  • 3. devops Cultural and Professional Movement http://www.youtube.com/watch?v=Fx8OBeNmaWw Adam Jacob
  • 4. My Background • Independent consultant • Have worked in different roles • Agile and Infrastructure • Just Enough Developed Infrastructure - http://jedi.be • Started organizing devopsdays • Recently joined Cutter Consortium
  • 5. Background check? analysts database developer security operations middleware testers sales network manager storage hr people
  • 6. The movement is inclusive Awesome Happy Cool Built neat stuff! Adam Jacob
  • 8. There are exclusive people Grumpy Tool Centric Us vs Them I’m a devop you’re a sysadmin Adam Jacob
  • 10. Looking for tools? You can still leave ...
  • 11. DEV OPS The problem
  • 12. “It’s NOT a technical problem”
  • 13. “It’s a human problem”
  • 14. We don’t trust We don’t trust the guys from the guys from operations. development. They suck They suck We don’t trust the guys from management. They suck
  • 15. Premise today “It’s a trust problem”
  • 16. Starting a devops culture = restoring trust http://voetstappen.blogspot.com/
  • 18. Traditional Business Formula (Strategy X Execution) = Results
  • 20. of Trust (-) Trust = (-) Speed (+) Cost (+) Trust =(+) Speed!(-) Cost!
  • 21. Tax Dividend • 10 x 10 = 100 (- Tax 40 %) = 60 • 10 x 10 = 100 (- Tax 10 %) = 90 • 10 x 10 = 100 (+ Div 20%) = 120
  • 22. Trust = f(character, competence)
  • 23. Waves of Trust Self Relationship Organizational Market Societal
  • 25. “We trust people, who make things happen”
  • 27. “We judge others by their behavior, we judge ourselves by our intentions”
  • 28. Principle of Credibility “The 4 Cores” • Trust = f(character, competence) • Character = f(integrity, intent) • Competence = f(capabilities, results)
  • 30. Ah, so this is where the (cool)tools come in !
  • 31. Chef Ruby Mysql Linux Puppet Java Redis Mac OSX Event EC2 Machine Node.js I <3 technology Vmware Fog Nginx Vagrant Sinatra Jclouds Thin Virtualbox Rails
  • 33. Technology Management But there’s a *lot* more Social Financial Communication
  • 34. WTF, do I need to learn all that?
  • 35. Broader knowledge, will make your actions more balanced
  • 36. It’s NOT about devs taking over ops or ops taking over devs.
  • 37. It’s about collaboration with people you trust.
  • 38. Results: • Take responsibility for results not just your action. Avoid , my job is only to ... • Expect to finish the job • Finish strong
  • 40. Make a personal backlog • Plan an item you can really make happen • No too big, make it feasible • (Result)Define what you want to achieve • (Competence)Learn what you need • Do : trust comes if you make things happen • Check the result • Act on it
  • 41. As a person • I want to develop these capabilities • I want to achieve results • When I fail , I want to learn and improve!
  • 42. As a manager, I want to • help people develop these capabilities • help people achieve results • (support the people) • help people fail and learn and improve! (+) Trust =(+) Speed!(-) Cost!
  • 44. Reach out to others
  • 45. Agile already did a great job
  • 46. Get together find allies forward links organize meetups distribute books find people with real issues kindly ignore nay sayers (for now)
  • 47. You can use technology to get the conversation started • Continuous Delivery • Testing, Monitoring • Automation • Fixing a problem • Scalability • Infrastructure as code • Performance • <whatever>
  • 48. “Seek to establish trust” Technology Trust by Testing, Monitoring Human Trust by Behavior
  • 49. 13 Behaviors “trust is established through action” • Needs to be • Sweet Spot balanced (Strength) • Too Little • Too much (Weakness) (Weakness) • f.i. talk straight vs demonstrate respect
  • 50. #1 Talk Straight • We really need this tool vs I want to learn this tool • It needs to be finished by X (that leaves me some time) • The user/my boss wants this now • It’s urgent, it’s important
  • 51. #2 Demonstrate Respect • we judge a person’s character, by how he treats people who can’t help or hurt him • little things , making things helpful
  • 52. #3 Create Transparency • no more Bob’s directory • check in your code • expose logfiles, config files ... • visualize progress (Kanban, Burndown) • share your information • make results repeatable
  • 53. #4 Right wrongs “to know what is right and not to do it is the worst cowardice” - Confucius • when you know there is a short cut, fix it and don’t leave it • fix a bug when it occurs, write a test • fix it, fix it all the way
  • 54. #5 Show loyalty • give credits • talk as if people were present • represent others
  • 55. #6 Deliver Results • Clarify Results upfront • your definition vs my definition • Small steps = Validation test (Userstories)
  • 56. #7 Get Better “Illiterate are those who can not learn, unlearn, relearn” - Alvin Toffler • seek feedback (Retrospectives) • learn from mistakes (5 whys) • ask: what to continue, what to stop, what to start now! • metrics (Neutral , not emotional) • change the system (Systems Thinking)
  • 57. #8 Confront Reality • avoid 99% finished • burn down chart • only measure of progress is working software (in production)
  • 58. #9 Clarify Expectations • deadlines vs. cut corners (win-win or no deal), negotiate them (who vs trust) • talk to devs, what do they expect • talk to admins, what do they expect • talk to customers
  • 59. #10 Practice Accountability • Accountability requires facing Truth • yourself and others • Don’t blame others , no pointing fingers
  • 60. #11 Listen First “If there is any secret, it lies in the ability to put yourself in the other person’s place” - Henry Ford
  • 61. #12 Keep Commitments • don’t PR your way out • make them careful • group is committed to results (not manager) • mgt supports team to keeping commitments
  • 62. #13 Extend Trust • Make it an action • here is the password • here is the code • everybody can check in and deployed to prod (with tests :) remember it’s inclusive not exclusive!
  • 63. As a person, • Given my capabilities • I want to practice these 13 behaviors • Help others to practice these 13 behaviors
  • 64. As a manager, I want to encourage behavior that increases trust (+) Trust =(+) Speed!(-) Cost!
  • 65. “Don’t change culture, change behavior!”
  • 66. Organizational Trust Eli mi na • Redundancy te Ta xe • Bureaucracy s • Politics • Disengagements (quit and stay) • Turnover (employee) • Churn (stakeholders) • Fraud
  • 68. Want to know more? #devops on twitter & irc http://devopsdays.org http://devopscafe.org http://planetdevops.net devops googlegroup devops-toolchain googlegroup
  • 70. Thank you! Patrick Debois - http://jedi.be/blog - @patrickdebois