Measuring dev ops vital signs

842 views

Published on

DevOpsDays London 2013 presentation.

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
842
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
12
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • I
  • Measuring dev ops vital signs

    1. 1. John Clapham & Paul Swartout Nokia Entertainment Checking DevOps’ vital signs - how healthy is your culture?
    2. 2. • This is the story of our foray into [devops] culture monitoring… © 2013 Nokia
    3. 3. • Disclaimer: © 2013 Nokia
    4. 4. © 2013 Nokia We don’t know what we’re talking about…
    5. 5. …or at least we’re not experts © 2013 Nokia We don’t know what we’re talking about…
    6. 6. The order of things… • Reasonings – why we started • Identifyings – Choosing what to measure • Data things – What we actually measured • Findings – What we found from data • Learnings – What we learnt from data and doing. © 2013 Nokia
    7. 7. Reasonings… © 2013 Nokia
    8. 8. © 2013 Nokia Has including everyone worked? 6 releases / 140 components January to December 2010 246 releases / 246 components January to October 2011
    9. 9. Voices in our heads whispered…
    10. 10. Are we getting complacent? ….and would we actually notice? © 2013 Nokia
    11. 11. • We knew the answers for our systems, but not our culture • Could we monitor culture? • If we monitored culture we could learn about health • We could keep fit… © 2013 Nokia
    12. 12. © 2013 Nokia
    13. 13. • But monitoring culture is hard. © 2013 Nokia
    14. 14. There are some measures already: • Organisational Health Index • Agile & Scrum Checklists • DevOpsDays Boston Open space © 2013 Nokia
    15. 15. What is culture anyway? © 2013 Nokia
    16. 16. What does a DevOps culture look like anyway? © 2013 Nokia Dev Land Ops World
    17. 17. Indentifyings… © 2013 Nokia
    18. 18. Why do people get into Dev Ops? © 2013 Nokia
    19. 19. Its all about improving… Efficiency Enjoyment Quality Security Up time, response time Delivery & Deployment time …some of these will be our vital signs © 2013 Nokia
    20. 20. Turning those motivations into Vital Signs could be challenging… © 2013 Nokia
    21. 21. What makes a good vital sign? • Applicable to different organisation sizes • Applicable to varying levels of maturity • Not prescriptive • Not judgemental • Low to no cost © 2013 Nokia
    22. 22. Vital Sign 1 – (Dev) Cycle Time • Average time between start of development and delivery to production. © 2013 Nokia
    23. 23. Vital Sign 2 – Shared Purpose • Are all of engineering working towards the same goals? © 2013 Nokia
    24. 24. Vital Sign 3 – Motivation • Is everyone motivated to learn and improve ways of working? © 2013 Nokia
    25. 25. Vital Sign 4 – Collaboration. • Do people work together willingly? © 2013 Nokia
    26. 26. Vital Sign 5 – Effectiveness • How much time spent actually adds value? © 2013 Nokia
    27. 27. Data-things… © 2013 Nokia
    28. 28. How do you get data? • Conversation & Interview • Questionnaires • Raw Data • Observations & spying © 2013 Nokia
    29. 29. The art of the question • Don’t lead the witness • Leave yourself room to be surprised • Be exacting © 2013 Nokia
    30. 30. © 2013 Nokia Where knowledge of production systems and applications is required to solve a live problem, would you say there is effective collaboration between engineers?
    31. 31. Findings © 2013 Nokia
    32. 32. Vital Sign 3 – Motivation © 2013 Nokia 0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% Dev Ops Other Do you believe there are opportunities to improve ways of working? Yes No Maybe
    33. 33. Vital Sign 5 – Effectiveness © 2013 Nokia 0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% Dev Ops Other How is your working time spent? Improvements Stability Waste
    34. 34. We also asked a referential question… What is in your way?
    35. 35. What’s in your way? Common themes: • No Time • Pressure to focus on features • Nothing © 2013 Nokia
    36. 36. What’s in your way? • “Convincing others to agree to any proposed changes!” • “Engineers who are busy or less cooperative” • “Technology, tools, understanding the technology from the ops perspective” © 2013 Nokia
    37. 37. Learnings… © 2013 Nokia
    38. 38. • People were happy to participate! © 2013 Nokia
    39. 39. • Our DevOps culture is healthy… © 2013 Nokia
    40. 40. • We’ve established a baseline • Talking about, and gathering data has been as valuable as the data itself • Open (but not measurable questions) were insightful. © 2013 Nokia
    41. 41. • We asked one more question © 2013 Nokia
    42. 42. • Do you have any comments, or suggestions, about this questionnaire? © 2013 Nokia
    43. 43. © 2013 Nokia
    44. 44. “No.” © 2013 Nokia
    45. 45. “Aim is unclear” © 2013 Nokia
    46. 46. “Some questions are too similarly worded, turns into a game of spot the difference, increasing amount of work to understand the question rather than answering it.” © 2013 Nokia
    47. 47. “It might be interesting to do something similar for the relationship between engineers and other parts of the business.” © 2013 Nokia
    48. 48. Concludings… © 2013 Nokia
    49. 49. • Measuring culture is hard …but rewarding! © 2013 Nokia
    50. 50. • Would you recommend it to a friend? © 2013 Nokia
    51. 51. • We learnt a lot about [DevOps] culture by creating our vital signs. • We gained insight and workable ideas from data and open questions. • More people are thinking about DevOps. © 2013 Nokia
    52. 52. © 2013 Nokia Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Health 2013-2014 Collaboration Motivation Shared purpose Engagement Effectiveness
    53. 53. • What vital signs would you look for? © 2013 Nokia
    54. 54. john.clapham@nokia.com @JohnC_Bristol paul.swartout@nokia.com @pswartout

    ×