Miniature Guide to Operational Features - EdinDevOps - SkeltonThatcher
•
0 likes•884 views
Treating operational aspects of software as 'non-functional requirements' and 'an Ops problem' rather than a core part of the software product leads to poor live service and unexplained errors in Production. However, many Product Managers understandably feel uneasy about taking on the (necessary) responsibility for prioritising operational features alongside user-visible and API features. This session aims to bring Scrum Masters and Product Owners up to speed on operational features, empowering them to make effective prioritisation choices about all kinds of product features, whether user-visible or operational.
Report
Share
Miniature Guide to Operational Features - EdinDevOps - SkeltonThatcher
- 1. The Miniature Guide to Operational Features Edinburgh DevOps Meetup – 15th September 2015 Rob Thatcher & Matthew Skelton
- 2. “Operational Features” how to develop and test prioritisation techniques
- 3. availability is the best feature
- 5. “the properties of a system which make it work well in Production”
- 6. Not PIMP MY RIDE MORE Greasy Mechanic
- 7. Not PIMP MY RIDE MORE Greasy Mechanic
- 8. Terminology
- 9. what happened to NFRs? (non-functional requirements)
- 11. language impact
- 13. nonsense !
- 16. How did we get to this?
- 17. admission: IT folk have been guilty of making operational features quite scary & mysterious
- 19. long lists of requirements crazy test plans
- 20. poor explanation of needs failure to engage stakeholders gold-plating
- 23. better approach pragmatic and effective rapid, safe, valuable
- 24. “the properties of a system which make it work well in Production”
- 29. non-linear increase in complexity and problems
- 31. we can no longer deal manually with the scale/volume of potential problems
- 33. agility and response to incidents
- 35. remote car hacking: security as an operational feature
- 36. HA + DR + Backup + Metrics + Diagnostics + …
- 38. think: "when it fails, how will we recover?“ it will fail
- 39. How do we develop and test Operational Features?
- 40. defined features testable and measurable
- 42. ahead lie the ‘ilities’...
- 43. 1. What 2. How to test
- 48. Configurability
- 50. re-read config (SIGHUP) text files in version control inject settings – no ‘black boxes’
- 52. toggle features via config “Postcode lookup unavailable” better UX
- 53. Deployability
- 55. immutable artefacts concurrent releases (SxS) symlinks
- 57. Maintainability
- 59. holding page as MVP!
- 60. live system component diagrams
- 61. modularity ability to upgrade version numbering (SemVer?)
- 62. Testability
- 64. every component has a /health endpoint
- 66. Recoverability
- 67. asynchronous service start expect services to be erroring logs are not wiped (rotated: okay) avoid flooding logs
- 69. no nasty zombies after failures MTTR more important than MTBF* * for most kinds of F
- 70. Performance
- 72. run key 'hotspot' areas early use a deployment pipeline ‘critical path’
- 74. early pipeline tests act as a barometer for later performance problems
- 76. derive transit time metrics
- 77. Monitorability
- 79. stream of metrics transaction tracing
- 83. Resilience
- 85. Saboteur for network failure testing deployment pipeline
- 86. assume missing or failing Chaos Monkey don’t crash on HTTP 503
- 87. Scalability
- 89. concurrent workers queues and bottlenecks throttling is your friend
- 93. securability by practice SSL certs & HEARTBLEED
- 95. # nmap-simple.attack Feature: simple nmap attack to check for open ports Background: Given "nmap" is installed And the following profile: | name | value | | hostname | example.com | Scenario: Check standard web ports When I launch an "nmap" attack with: """ nmap -F <hostname> """ Then the output should match /80.tcps+open/ Then the output should not match: """ 25/tcps+open """
- 96. Availability
- 98. “available but unusable" synthetic transactions
- 99. special HTTP header: trigger additional metrics/reporting
- 100. How the organisation affects Operational Features
- 101. Budgets
- 102. bonuses: story points delivered tickets closed
- 103. Capex vs Opex tax breaks
- 104. avoiding the Capex/Opex evil
- 105. Developers seen as more valuable than Ops people 3x hiring bonus for Devs (!)
- 106. improved awareness in product teams
- 108. share ownership and decision making
- 112. Product Owner on call for incidents
- 113. tricky! high degree of maturity honesty about the product
- 114. Product Owner and Tech Lead are both on the hook for outages
- 115. AVOID Product Owner for ‘user features’ and Tech Lead for ‘operational features’
- 116. How to evaluate Operational Features vs User Features
- 117. treat Ops team folk as another user persona
- 119. alternatives to User Stories?
- 120. NOT: "as a logging subsystem, I want..."
- 121. Metrics
- 122. Live: downtime, A/B for operational aspects (speed) Pre-live: time spent re-deploying
- 124. metric-ify your delivery and test infrastructure 99.99% uptime, but 20 redeployments every time
- 126. Heuristics for operational features 30% of total product budget 30% of dev team time
- 128. MVP: ‘service unavailable’ page
- 129. test early for operational features using a deployment pipeline
- 130. single product backlog: (user) features + (operational) features
- 131. availability is the best feature