2013 Software Development Meeting: Continuous Delivery - To Have or Have Not (Slides)
Monday, July 29, 2013
Every development team is being asked to increase its development speed and scalability either to push themselves to get code out quicker and reduce risk of large deployments or to meet the increasing demand of the market for new capabilities faster. Tools such as Scrum, Agile and Continuous Delivery are in play or are becoming the norm to enhance overall productivity. The use of continuous delivery pushes teams through a different process enabling them to ship once, many or hundreds (yes, hundreds!) of times per day.
Damon Poole (@damonpoole), Chief Agilist at Eliasen Group set the stage for MassTLC’s software development meeting with an overview of Continuous Delivery (CD) and the tools and strategies needed to move to CD to make more money. He reminded us that we should all be measured on business value delivery not on how many lines of code are written or how many bugs are fixed. View David's slides below.
Next, Aaron White (@aaronwhite) from Boundless, a start-up in Boston that makes textbooks free online for college students, discussed their implementation of the entire suite of agile strategies, from CD to Continuous Integration to Kanban. They average 10+ deployments per day and every team member takes ownership from conception to deployment including development, testing, QA and also customer support. To support this they widely use automated testing. They built an internal dashboard to manage their change log, which is crucial to managing what’s going out the door. He also highly recommends Trello as a helpful Kanban project management tool. View Aaron's slides below.
Chad Pytel (@cpytel) from ThoughtBot, a consulting shop in Boston that builds web and mobile apps on Ruby, has two roles for employees at his company: either designer or developer. There is no QA stage as developers have to write their own tests, a practice critical to the success of CD. They deliver daily but do weekly retrospectives. They built their own project management tool that is hugely successful for planning time, setting schedules and priorities. Of note, they have a great 3 month training and mentoring program in place to find top talent! View Chad's slides below.
Elias Torres (@eliast), joined us from Hubspot. At $65M in revenue, they have only 45 engineers and work in small, three-person teams. Each team defines their own process for scheduling & prioritizing engineers and own their products from code to operations. They seem to win the prize for most deployments as they deploy 100+ times per day. Elias did note that going fast is great but also has its price. He says, "We break shit all the time - but we also fix things very quickly.” The amount of change between deployments is so small they can either roll back to the last deploy or fix very quickly. They have also found that sometimes, the amount of change can be difficult for customers. Communications with the rest of the company and their customers is critical. What keeps Elias up at night? If they slow down, the fixes will all be bigger and more could be broken. "We focus on developer productivity. We automate everything except writing new code,” concludes Elias. View Elias' slides below.