Technology for Digital products

Technology for Digital products

A deck used for workshops for service managers of Government services, helping them work better with technology colleagues and to introduce them to some of the challenges.

98234c645fe8c935edc0fec0186d28b8?s=128

Gareth Rushgrove

February 06, 2014
Tweet

Transcript

  1. GDS Technology for Digital! Gareth Rushgrove Questions for Service Managers

    Questions for Service Managers
  2. GDS Gareth Rushgrove Gareth Rushgrove! Technical Architect! Government Digital Service!

    @garethr
  3. What is this about? (the introduction) GDS Gareth Rushgrove

  4. GDS Gareth Rushgrove

  5. 2 Assemble a multidisciplinary team who can design, build and

    operate the service, led by a single, suitably skilled and empowered Service Manager GDS Gareth Rushgrove
  6. 5 Consider the tools and systems they will be using

    to build, host, operate and measure their service, and how to procure them GDS Gareth Rushgrove
  7. 14 Make sure you have the capacity and technical flexibility

    to update and improve the service on a very frequent basis GDS Gareth Rushgrove
  8. 15 Make all new source code open and reuseable, and

    publish it under appropriate licences ! ! (or have provided a convincing explanation of why this cannot be done for specific subsets of the source code) GDS Gareth Rushgrove
  9. What roles do we have on the team?! ! What

    technology are we using?! ! What are the risks with that?! ! What happens when we have a problem at 2am? ! ! How do we change things over time? GDS Gareth Rushgrove
  10. What roles do we have on the team?! ! What

    technology are we using?! ! What are the risks with that?! ! What happens when we have a problem at 2am? ! ! How do we change things over time? GDS Gareth Rushgrove
  11. What roles do we have on the team?! ! What

    technology are we using?! ! What are the risks with that?! ! What happens when we have a problem at 2am? ! ! How do we change things over time? GDS Gareth Rushgrove
  12. What roles do we have on the team?! ! What

    technology are we using?! ! What are the risks with that?! ! What happens when we have a problem at 2am? ! ! How do we change things over time? GDS Gareth Rushgrove
  13. What roles do we have on the team?! ! What

    technology are we using?! ! What are the risks with that?! ! What happens when we have a problem at 2am? ! ! How do we change things over time? GDS Gareth Rushgrove
  14. What roles do we have on the team? (getting the

    right mix of skills) GDS Gareth Rushgrove
  15. GDS Gareth Rushgrove Developers

  16. GDS Gareth Rushgrove

  17. GDS Gareth Rushgrove Web operations

  18. GDS Gareth Rushgrove

  19. GDS Gareth Rushgrove Technical architects

  20. GDS Gareth Rushgrove Likely more experienced developers or web operations

    engineers
  21. GDS Gareth Rushgrove Other specialists! on the team

  22. GDS Gareth Rushgrove Not just visitors

  23. GDS Gareth Rushgrove Design your technical organisation

  24. GDS Gareth Rushgrove Depends on size of team and size

    of department or agency
  25. GDS Gareth Rushgrove Individuals with different experience, skills and specialisms

  26. GDS Gareth Rushgrove The unit of delivery is the team

  27. GDS Gareth Rushgrove An example programme

  28. GDS Gareth Rushgrove From one team of about 14

  29. GDS Gareth Rushgrove Product owner Delivery manager Developer Developer Developer

    Developer Developer Content designer Content designer Content designer Designer Developer Developer Developer
  30. GDS Gareth Rushgrove To 140 people in 14 teams

  31. GDS Gareth Rushgrove Product owner elivery manager Developer Developer Developer

    Developer Developer Product owner Delivery manager Designer Developer Developer Content designer Developer Content designer Business analyst Product owner Delivery manager Developer Developer Developer Developer Developer Business analyst Product owner Delivery manager Developer Developer Developer Developer Developer Product owner Delivery manager Designer Developer Content designer Content designer Content designer Content designer Business analyst Content designer
  32. GDS Gareth Rushgrove Web operations team just another product team

  33. GDS Gareth Rushgrove Product owner elivery manager Developer Developer Developer

    Developer Developer Product owner Delivery manager Designer Developer Developer Content designer Developer Content designer Business analyst Product owner Delivery manager Developer Developer Developer Developer Developer Business analyst Product owner Delivery manager Developer Developer Developer Developer Developer Product owner Delivery manager Designer Developer Content designer Content designer Content designer Content designer Business analyst Content designer Product owner Delivery manager Web operations Web operations Web operations Web operations Web operations Web operations Web operations
  34. GDS Gareth Rushgrove With web operations people in other teams

    when required
  35. GDS Gareth Rushgrove Product owner elivery manager Developer Developer Developer

    Developer Developer Product owner Delivery manager Designer Developer Developer Content designer Developer Content designer Business analyst Product owner Delivery manager Developer Developer Developer Developer Developer Business analyst Product owner Delivery manager Developer Developer Developer Developer Developer Product owner Delivery manager Designer Developer Content designer Content designer Content designer Content designer Business analyst Content designer Web operations Web operations
  36. GDS Gareth Rushgrove And with developers also working on operations

    tasks
  37. GDS Gareth Rushgrove And people rotated between teams periodically

  38. What technology are we using? (how to help choose technology)

    GDS Gareth Rushgrove
  39. GDS Gareth Rushgrove Any technology choice is a future constraint

  40. GDS Gareth Rushgrove Focus on the ability to change

  41. GDS Gareth Rushgrove Avoiding lock-in

  42. GDS Gareth Rushgrove Buy vs build vs integrate

  43. http://www.flickr.com/photos/psd/9122642253 GDS Gareth Rushgrove

  44. GDS Gareth Rushgrove Encourage technical team members to think about

    cost
  45. GDS Gareth Rushgrove Financial, support, available skills, hiring

  46. GDS Gareth Rushgrove Encourage management or procurements colleagues to consider

    user experience
  47. Exercise: Choosing a database? GDS Gareth Rushgrove

  48. GDS Gareth Rushgrove

  49. GDS Gareth Rushgrove Type of data?

  50. GDS Gareth Rushgrove Relational, Graph, Document,! Key-Value...

  51. GDS Gareth Rushgrove Science?

  52. GDS Gareth Rushgrove Brewers theorem

  53. GDS Gareth Rushgrove Consistency, Availability, Partition tolerance

  54. GDS Gareth Rushgrove Performance?

  55. GDS Gareth Rushgrove Resilience?

  56. GDS Gareth Rushgrove Familiarity?

  57. GDS Gareth Rushgrove API?

  58. GDS Gareth Rushgrove Cost?

  59. GDS Gareth Rushgrove Licensing cost? Hardware cost? Operating cost? Development

    cost?
  60. GDS Gareth Rushgrove Avoid cargo-culting

  61. What are the risks with that? (risk management and information

    assurance) GDS Gareth Rushgrove
  62. Security is! everyone’s job GDS Gareth Rushgrove

  63. Confidentiality! Integrity! Availability GDS Gareth Rushgrove

  64. Don’t just rely on the formal process GDS Gareth Rushgrove

  65. But do understand and use the existing risk management apparatus

    GDS Gareth Rushgrove
  66. GDS Gareth Rushgrove

  67. Assurance GDS Gareth Rushgrove

  68. Accreditation GDS Gareth Rushgrove

  69. IS1 and IS1 GDS Gareth Rushgrove

  70. Baseline control set GDS Gareth Rushgrove

  71. GDS Gareth Rushgrove

  72. Good Practice Guides (GPGs) GDS Gareth Rushgrove

  73. Protective marking scheme GDS Gareth Rushgrove

  74. Existing:! Top secret! Secret! Restricted! Confidential! Protect GDS Gareth Rushgrove

  75. New:! Top secret! Secret! Official GDS Gareth Rushgrove

  76. Business Impact Levels GDS Gareth Rushgrove

  77. The problem with Business Impact Levels GDS Gareth Rushgrove

  78. GDS Gareth Rushgrove Information Security

  79. What happens when we have a problem at 2am? (Operating

    a 24/7 service) GDS Gareth Rushgrove
  80. GDS Gareth Rushgrove Incident management

  81. GDS Gareth Rushgrove What types of incidents can’t wait until

    the morning?
  82. GDS Gareth Rushgrove On-call vs staffed

  83. GDS Gareth Rushgrove Employment contracts

  84. Exercise: What to monitor? GDS Gareth Rushgrove

  85. GDS Gareth Rushgrove Example GOV.UK

  86. 30,000+ metrics collected, many every second GDS Gareth Rushgrove

  87. ~2000 checks, most every few minutes GDS Gareth Rushgrove

  88. GDS Gareth Rushgrove http://www.flickr.com/photos/psd/8756580339 Lots of information on dashboards

  89. GDS Gareth Rushgrove What would you monitor? Interstellar spacecraft license

    Space interstellar-spacecraft-license
  90. How do we change things over time? (change control and

    release management) GDS Gareth Rushgrove
  91. GDS Gareth Rushgrove http://www.flickr.com/photos/psd/9099796942

  92. GDS Gareth Rushgrove

  93. GDS Gareth Rushgrove GOV.UK averages about 6 releases a day

  94. GDS Gareth Rushgrove We changed less software on the day

    of launch than probably any day before or since
  95. GDS Gareth Rushgrove Release pipeline

  96. GDS Gareth Rushgrove

  97. GDS Gareth Rushgrove One click deploy

  98. GDS Gareth Rushgrove One click deploy with suitable processes and

    access controls
  99. GDS Gareth Rushgrove Zero click deploy for early parts of

    pipeline
  100. GDS Gareth Rushgrove Pipeline visibility

  101. GDS Gareth Rushgrove One place! to deploy

  102. GDS Gareth Rushgrove App showing deploys

  103. GDS Gareth Rushgrove CMDB

  104. GDS Gareth Rushgrove Engage with wider processes

  105. GDS Gareth Rushgrove 1. Transition planning and support! 2. Change

    management! 3. Asset and configuration management! 4. Release and deployment management! 5. Service validation and testing! 6. Change evaluation! 7. Knowledge management
  106. GDS Gareth Rushgrove Share language

  107. GDS Gareth Rushgrove Regular releases reduce risk

  108. GDS Gareth Rushgrove Practice makes perfect

  109. Next steps (Further reading) GDS Gareth Rushgrove

  110. GDS Gareth Rushgrove CTO Guidance

  111. GDS Gareth Rushgrove Choosing Technology

  112. GDS Gareth Rushgrove

  113. GDS Gareth Rushgrove

  114. GDS Gareth Rushgrove

  115. GDS Gareth Rushgrove

  116. GDS Gareth Rushgrove

  117. Questions? (And thanks for listening) GDS Gareth Rushgrove

  118. GDS Gareth Rushgrove Gareth Rushgrove! Technical Architect! Government Digital Service!

    @garethr