Java Tech & Tools | Continuous Delivery - the Writing is on the Wall | John Stevenson
•
2 j'aime•1,554 vues
2011-11-01 | 10:40 AM - 11:40 AM So you want to do continuous delivery but is it working and how does the team and the organisation know what's going on? Using wallboard, information radiators and even just bits of paper stuck to the wall can help you manage all your development. Covering the many ways companies have visualised the mashinations of their work and providing tips on setting up your own uber information radiators.
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
En vedette (20)
Similaire à Java Tech & Tools | Continuous Delivery - the Writing is on the Wall | John Stevenson
Similaire à Java Tech & Tools | Continuous Delivery - the Writing is on the Wall | John Stevenson (20)
Plus de JAX London
Plus de JAX London (20)
Dernier
Dernier (20)
Java Tech & Tools | Continuous Delivery - the Writing is on the Wall | John Stevenson
- 1. Continuous Deployment The writing is on the wall John Stevenson Lean Agile Machine ©LeanAgileMachine Creative Commons Licence
- 2. Who is John Stevenson ● Lean agile coach Kanban, system thinking, ToC. ● Atlassian ambassador in UK Growing communities around JIRA... ● Community geek London Java, Graduate Devs, London Scala, London Clojurians, etc. ● Dabbles with ©LeanAgileMachine Creative Commons Licence
- 3. My Journey ● Started with RUP, UML & XP ● Fell for Behaviour Driven Development & kanban ● Learn about a lot of Value & Systems thinking ● Coached teams & individuals ● Sharing experiences with community ©LeanAgileMachine Creative Commons Licence
- 4. So what is Continuous Deployment ? ©LeanAgileMachine Creative Commons Licence
- 5. ...its incredibly hard ©LeanAgileMachine Creative Commons Licence
- 6. ...even if you are... ©LeanAgileMachine Creative Commons Licence
- 7. ...hard plus infinity for everyone else ©LeanAgileMachine Creative Commons Licence
- 8. Continuous deployment example: ©LeanAgileMachine Creative Commons Licence
- 10. Typically: 25 deploys per day per developer ©LeanAgileMachine Creative Commons Licence
- 12. So why go for continuous deployment? ©LeanAgileMachine Creative Commons Licence
- 17. http://blog.thehigheredcio.com/2011/08/31/efficiency-vs-effectiveness/ ©LeanAgileMachine Creative Commons Licence
- 18. Understanding the business Table stakes / foundations Differentiators Spoilers Accelerators ©LeanAgileMachine Creative Commons Licence
- 21. Where to get started ?? ©LeanAgileMachine Creative Commons Licence
- 22. Is your team / company ready ? A case study in pain and dissapointment! ©LeanAgileMachine Creative Commons Licence
- 23. Change can be expensive ©LeanAgileMachine Creative Commons Licence
- 24. A long journey of discovery ©LeanAgileMachine Creative Commons Licence
- 25. Involving the whole business ©LeanAgileMachine Creative Commons Licence
- 26. Understanding of Value ©LeanAgileMachine Creative Commons Licence
- 27. The right motivation ©LeanAgileMachine Creative Commons Licence
- 28. What is the goal? ©LeanAgileMachine Creative Commons Licence
- 29. Where to start ?? ©LeanAgileMachine Creative Commons Licence
- 30. Visualise how you do IT... ©LeanAgileMachine Creative Commons Licence
- 31. Kanban – a wall of Facts ©LeanAgileMachine Creative Commons Licence
- 32. Let the board show issues... V1.0.1, V1.0.2, V1.0.3, V1.0.4, Build 1209 Build 1221 Build 1301 ©LeanAgileMachine Creative Commons Licence
- 33. Value stream mapping The (often wide) path to getting things done Activities that get things done effectively ©LeanAgileMachine Creative Commons Licence
- 37. Include the whole process... Strategy to shiped Budgeting Business sign off Deployment dry run ©LeanAgileMachine Creative Commons Licence
- 38. Improve the foundations ©LeanAgileMachine Creative Commons Licence
- 39. Monitoring your servers ● Nagios / NagVis ● The Dude ● Microsoft Operations Manager ● Outsource IT... ©LeanAgileMachine Creative Commons Licence
- 45. Sever Provisioning ©LeanAgileMachine Creative Commons Licence
- 46. Its all virtual these days... ©LeanAgileMachine Creative Commons Licence
- 48. Virtual Machines Automate provisioning Manage sys-admin tasks remotely Spin up instances into the cloud Using public cloud when your private cloud is maxed out Off the shelf pre-configured servers ©LeanAgileMachine Creative Commons Licence
- 49. Managing VM's is easy ©LeanAgileMachine Creative Commons Licence
- 50. Automating Virtual Machines ©LeanAgileMachine Creative Commons Licence
- 51. Vagrant – simple to use ● Requirements Ruby Virtualbox Chef / Puppet for other VM systems ©LeanAgileMachine Creative Commons Licence
- 53. Automated server management Puppet / Chef / Rex ©LeanAgileMachine Creative Commons Licence
- 54. Disaster recovery for learning ©LeanAgileMachine Creative Commons Licence
- 55. Change freezes The period of time when the most of the changes happen When lots of patches are done ! A good time to learn what is important ! ©LeanAgileMachine Creative Commons Licence
- 56. Deployment Strategies ©LeanAgileMachine Creative Commons Licence
- 57. If it hurts, do it more often ©LeanAgileMachine Creative Commons Licence
- 58. Segmented deploys Different customers / different expectations ©LeanAgileMachine Creative Commons Licence
- 59. Timely deployments Cost of delay ? When is the software valuable ? ©LeanAgileMachine Creative Commons Licence
- 61. Visualise deployment strategies?? ©LeanAgileMachine Creative Commons Licence
- 62. Managing your code ©LeanAgileMachine Creative Commons Licence
- 63. It compiles, ship it!! Ship It Compile ©LeanAgileMachine Creative Commons Licence
- 64. Automated builds Design around common patterns for building Should have valuable reason for doing something different SBT ©LeanAgileMachine Creative Commons Licence
- 65. Simple Maven config <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>com.mycompany.app</groupId> <artifactId>my-app</artifactId> <packaging>jar</packaging> <version>1.0-SNAPSHOT</version> <name>Maven Quick Start Archetype</name> <url>http://maven.apache.org</url> <dependencies> <dependency> <groupId>junit</groupId> <artifactId>junit</artifactId> <version>4.8.2</version> <scope>test</scope> </dependency> </dependencies> </project> ©LeanAgileMachine Creative Commons Licence
- 66. Local repositories Nexus Artefactory DVCS ©LeanAgileMachine Creative Commons Licence
- 67. Build tools – continuous feedback Maven 3 Shell Simple Build Tool ~Tests ©LeanAgileMachine Creative Commons Licence
- 68. Coding fast feedback JavaScript ©LeanAgileMachine Creative Commons Licence
- 69. Testable code ● TDD / BDD helped devs have a better appreciation of code that is more testable ● Faster feedback gave devs (and team) better understanding of what is needed ● Resolve issues quickly, prevent many from happening at all ● ©LeanAgileMachine Creative Commons Licence
- 70. Behaviour Driven Developent ©LeanAgileMachine Creative Commons Licence
- 71. Deployable software ● Automated server builds ● Automated deployment scripts / tools ● Automated tests / specifications ● Effective business review ● Faster feedback ● Resolve issues quickly ● Deploy when valuable ©LeanAgileMachine Creative Commons Licence
- 72. Distributed Versioning ● Smaller repositories Per component / module Simpler architecture ● Manage branching easier with pull requests A pull system is more effective than central push ● Different repos for different purposes Repo for deployment, trunk, CI server ©LeanAgileMachine Creative Commons Licence
- 74. Git Workflow ©LeanAgileMachine Creative Commons Licence
- 75. Git architecure (logical) ©LeanAgileMachine Creative Commons Licence
- 79. Code reviews DVCS push requests ©LeanAgileMachine Creative Commons Licence
- 80. Central or Distributed Version control ©LeanAgileMachine Creative Commons Licence
- 82. Centralised issues Fear of breaking the build unnecessary branching delayed commits Off-line support? Any redundancy in versioning server? ©LeanAgileMachine Creative Commons Licence
- 83. Managed Distributed team ©LeanAgileMachine Creative Commons Licence
- 84. Continuous Integration What When How long Run specifications / unit tests Reports Actions to initiate ©LeanAgileMachine Creative Commons Licence
- 85. CI Server basics ©LeanAgileMachine Creative Commons Licence
- 86. BOfH CI Server Kicks out checked in code if it fails Wires up build bunnies to stop you hiding from broken builds Wall of shame for breaking builds Top ten worst programmers ©LeanAgileMachine Creative Commons Licence
- 89. CI Server lights ©LeanAgileMachine Creative Commons Licence
- 91. Issue ticker Stream of issues flowing Highlight new features, overdue items, critical issues, time related news, etc ©LeanAgileMachine Creative Commons Licence
- 93. UltimateWallboard .com ©LeanAgileMachine Creative Commons Licence
- 94. More than compiling code... conf/tomcat-users.xml <user username=”bamboo” password=”bamboo” roles=”manager-script,manager-gui”/> ©LeanAgileMachine Creative Commons Licence
- 95. One click deploy ©LeanAgileMachine Creative Commons Licence
- 96. Architect for deployment Modular systems Simple interfaces Supported by acceptance tests (specifications) Automate low value tasks ©LeanAgileMachine Creative Commons Licence
- 98. Predictability / Cadence Smaller tasks Understanding you capacity ©LeanAgileMachine Creative Commons Licence
- 101. How will you make a change ? ● Automated deployments ● Distributed version control ● Refactoring architecture, design & code ● Modularity in design ● Migrating from technical debt ● Shouting... ©LeanAgileMachine Creative Commons Licence
- 103. Thank you ©LeanAgileMachine Creative Commons Licence
- 104. Feedback & Refs @JR0cket JStevenson@atlassian.com John@jr0cket.com Please note: Very few bulletpoints were hurt during the making of this presentation ©LeanAgileMachine Creative Commons Licence
- 105. The big-ish picture ©LeanAgileMachine Creative Commons Licence
- 106. Summary Adaptable practices TDD/BDD, DDD, kanban, ToC, system thinking Good understanding of supporting tools Cucumber, CI build jobs, DVCS, ... Strong DevOps capability Understand business value ©LeanAgileMachine Creative Commons Licence
- 107. A tool to collaborate ©LeanAgileMachine Creative Commons Licence
- 108. Visualising the workload ©LeanAgileMachine Creative Commons Licence
- 109. Pull system ©LeanAgileMachine Creative Commons Licence
- 110. Experditing ● Visualisation for a high priority task Big red sticker Experditing lane Record other tasks being blocked ● Review why you get high priority task Consider it a constraint / bottleneck ©LeanAgileMachine Creative Commons Licence
- 111. Experditing lane ©LeanAgileMachine Creative Commons Licence
- 112. DevOps Goal keeper ● Team rotates people around role ● Goalkeeper fields all issues ● Rest of team allowed to focus on a (bigger) task ● Use visual indicator to show who is the Goalie Visually represent these points ?? ©LeanAgileMachine Creative Commons Licence
- 113. Drop the Backlog ● The backlog is a omnipresent sign of overload Useful for pushing back to the management Bad for team moral Hide it away (eg. JIRA) ● When team are in tune with value, tasks flow more naturally – opportunities are not drowned out ©LeanAgileMachine Creative Commons Licence
- 114. Data dashboard effect ● Manager can instantly see what you are working on ● Manager can evaluate priorities easily Or go back and ask for clarification with business ● Gives data on issues Recording task swapping, time to work on tasks Data to review at retrospective on current approach ©LeanAgileMachine Creative Commons Licence
- 116. Washing line ©LeanAgileMachine Creative Commons Licence
- 117. RSPB Royal Society for the protection of Bulletpoints ©LeanAgileMachine Creative Commons Licence
- 118. Change at speed of deployment ©LeanAgileMachine Creative Commons Licence
- 119. Be as creative as needed ©LeanAgileMachine Creative Commons Licence
- 120. Managing the change ©LeanAgileMachine Creative Commons Licence
- 121. Subtle ”Theory of Constraints” ● What is stopping you achieve your goals ? Identify all the current challenges ● Find how to work effectively With respect to the biggest challenge ● Incrementally improve around biggest challenge ● Review the challenges ©LeanAgileMachine Creative Commons Licence
- 122. Change at the speed of acceptance ● Effective change cannot be pushed ● kanban estoles pull, change should be ● Odd that some pulled many agile projects start and end with a big bang ©LeanAgileMachine Creative Commons Licence
- 123. Lean Startup ● Business canvas model ● Real options ● Last responsible moment ● Least responsible change ©LeanAgileMachine Creative Commons Licence
- 124. Lessons from Service Desk ● Variation of personal kanban Sticky notes at the side of the keyboard One priority at once Need business reason to change priorities Record reason and number of times you had to revisit the task ©LeanAgileMachine Creative Commons Licence
- 125. DevOps overload ● Lots of last minute ● DevOps have no time to patches script deployments ● Have to deal with long, ● Deployment like boring deployment buses, nothing for a documents few days then three ● Repeatedly swiched from come at once for the infrastructure work, same night vastly increasing time taken. ©LeanAgileMachine Creative Commons Licence
- 126. Summary of Kanban ● Visualse work ● Manage WIP ● Helps you stay sane ● Engage with business ● Show you are Shared ownership productive ● Encourage realistic ● Deal with micro- priorities management ©LeanAgileMachine Creative Commons Licence