Ben Lidgey - DevOps in Disguise | Agile Delivery 2017
- 2. DevOps is all about culture
- 3. What are your aims? ● What do you want to achieve? ● When? ● How will you show it?
- 4. Audience ● Who are the audience? ● What do they know? ● How will you show the results? ● Is there a commitment from them?
- 5. What is the value? ● Financial ● Quality ● Rapid releases (customer benefits) ● Reputation ● Staff morale , engagement Make sure you have identified the metrics
- 6. DevOps is all about culture
- 9. DESC method D = Describe what happened E = Explain how this made you feel S = Share what you would like to happen (in the future) C = Compromise by stating what you will do as a result of this newer way
- 10. DESC method in DevOps context D = Describe what happened in previous work E = Explain the impact on the delivery S = Share the changes to the ways of working you would like to introduce C = Collaborate if you meet resistance
- 11. Describe: We currently spend at least 2 weeks in a test cycle at the end of the project
- 12. Explain: Project does not deliver working software regularly
- 13. Explain: Large effort at the end, with bugs often found just before the release date
- 14. Share: I want the teams to learn and implement automated testing
- 16. Compromise: Start with automated testing for happy path scenarios
- 17. Compromise: After the first feature is delivered we will demo it
- 19. 1 day
- 20. Conclusion ● Testing performance time reduced ○ Higher quality ● Team learning new tools and techniques ○ Morale and engagement ● Business seeing the benefits of investment ○ Deliver value to the customer
- 21. Summary ● Cultural change ● Small steps phrased for business ● Demonstrate results to the business ● Consider “D E S C”