Tesla and Adobe: Why Continuous Deployment May Mean Continuous Customer Disappointment

Steve Blank

In the last few years Agile and “Continuous Deployment” has replaced Waterfall and transformed how companies big and small build products. But businesses are finding that Continuous Deployment not only changes engineering but has ripple effects on the rest of its business model.

Why Continuous Deployment?

Startup Lessons Learned

Lessons Learned by Eric Ries Monday, June 15, 2009 Why Continuous Deployment? Of all the tactics I have advocated as part of the lean startup , none has provoked as many extreme reactions as continuous deployment , a process that allows companies to release software in minutes instead of days, weeks, or months. My previous startup, IMVU , has used this process to deploy new code as often as an average of fifty times a day.

Trending Sources

Continuous deployment for mission-critical applications

Startup Lessons Learned

Lessons Learned by Eric Ries Monday, December 28, 2009 Continuous deployment for mission-critical applications Having evangelized the concept of continuous deployment for the past few years, Ive come into contact with almost every conceivable question, objection, or concern that people have about it. Or, phrased more hopefully, "I see how you can use continuous deployment to run an online consumer service, but how can it be used for B2B software?"

Case Study: Continuous deployment makes releases non-events

Startup Lessons Learned

Lessons Learned by Eric Ries Monday, January 18, 2010 Case Study: Continuous deployment makes releases non-events The following is a case study of one entrepreneurs transition from a traditional development cycle to continuous deployment.

Tesla and Adobe: Why Continuous Deployment May Disappoint Customers

Inc Startups

How agile deployment of products can affect a company''s business model in unintended ways For the last 75 years, products (both durable goods and software) were built via waterfall development. Marketing delivers a "requirements" document to engineering.

Scaling CI at Etsy: Divide and Concur, Revisited

Code as Craft

The numerous jobs on our dashboard were great for pinpointing where the failures were, but it was difficult to determine at which stage of the deploy pipeline the failures existed. We needed some way to communicate the test status at each stage of the deployment pipeline.

Tracking Every Release

Code as Craft

Change to application code (deploys) are opportunities for failure. To track time-based events, the value sent for the metric can simply be “1″ Erik Kastner added this right into our code deployment tool so that every single deploy is automatically tracked. We can mix our code deployments right into the graph of PHP warnings we saw above. Combined with engineers pairing up for code reviews, we catch most issues before they get deployed.

PHP 16

Continuous deployment with downloads

Startup Lessons Learned

Lessons Learned by Eric Ries Monday, February 16, 2009 Continuous deployment with downloads One of my goals in writing posts about topics like continuous deployment is the hope that people will take those ideas and apply them to new situations - and then share what they learn with the rest of us. So I was excited to read a recent post about applying the concept of continuous deployment to that thickest-of-all-clients, the MMOG.

Lessons Learned: The engineering manager's lament

Startup Lessons Learned

Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their product development process. Last week, I found myself in a similar situation, but this time talking to the engineering manager. This engineering manager is a smart guy, and very experienced. And why is the engineering manager suffering so badly?

We Invite Everyone at Etsy to Do an Engineering Rotation: Here’s why

Code as Craft

At Etsy, it’s not just engineers who write and deploy code – our designers and product managers regularly do too. In the past year, 70 employees have completed engineering rotations. This includes time spent training and the deploy itself.

From Alpha to Beta: Continuous Deployment at Threadflip

Launching Tech Ventures

by Samantha Lynch & Elizabeth Trongone Having prior product management experience in companies like Birchbox, Warby Parker and Group Commerce, we sought to continue to hone our product management skills through the lens of Launching Technology Ventures. Throughout our time working with Threadflip, we collected learnings on working with engineers, recruiting users and administering tests and interviews. Certain critical pain points and areas of confusion came up continuously.

Engineering Social Commerce

Code as Craft

In this post we explore some of the engineering challenges we faced in building a social commerce feature like the gift recommender. At Etsy, we build our system in a continuously deployed environment which allows us to quickly iterate and experiment. This holiday season we launched a redesigned version of a product we call “Gift Ideas for Your Friends”.

Lessons Learned: Customer Development Engineering

Startup Lessons Learned

Lessons Learned by Eric Ries Sunday, September 7, 2008 Customer Development Engineering Yesterday, I had the opportunity to guest lecture again in Steve Blank s entrepreneurship class at the Berkeley-Columbia executive MBA program. In addition to presenting the IMVU case, we tried for the first time to do an overview of a software engineering methodology that integrates practices from agile software development with Steves method of Customer Development.

Optimizing for developer happiness

Code as Craft

In the talk, I go into the philosophical reasons why continuous deployment makes engineers happy, how radically decentralizing authority and thinking of your team as a community optimize for happiness, and the how our approach to tooling makes everything work. engineering philosophy videoA few weeks ago, I gave a talk at Railsconf in Baltimore about how we optimize for developer happiness at Etsy.

API First Transformation at Etsy – Operations

Code as Craft

Continuing down this path we would have exhausted space and power in our datacenters. It’s tied into our continuous deployment system, moving along with up to 60 deploys per day for etsy.com. api engineering infrastructure mobile operations philosophy API PHP

API 17

API First Transformation at Etsy – Concurrency

Code as Craft

Before we deploy code to Etsy.com, we check if the compiled routes and client code are up to date via Jenkins. And we neatly tie this into our continuous deployment process. api engineering infrastructure mobile philosophy

API 19

The Product Hacking Ecosystem

Code as Craft

Continuous deployment, the practice of pushing your code live the moment its ready, is absolutely essential for product hackers. engineering people philosophy bad idea mean time between failures meaningless death

Moving Fast at Scale: a microconference at SXSW

Code as Craft

We also deployed the site to production 517 times with changes from over 70 unique individuals. We’ve written about how we do it here on Etsy’s engineering blog (look here , here , and here for a sampling) but we’ve never explained it all in one place, in person, with free beer. “Continuous Deployment: the Why and How&# (Kellan Elliott-McCrea, VP of Engineering). Members of the Etsy engineering team will be hanging out.

Chad 11

Lessons Learned: SEM on five dollars a day

Startup Lessons Learned

Trying to answer that question at IMVU led me to discover Google AdWords and the world of search engine marketing. You declare how much someone clicking an advertisement is worth to you, and then the search engine does its best to get you as many clicks as it can at that price. Labels: search engine marketing 4comments: Tauya said. Case Study: Continuous deployment makes releases n.

SEM 20

Static Analysis for PHP

Code as Craft

They form an important part of our continuous deployment pipeline along with one-button deploys, fast unit and functional tests, copious amounts of graphing, and a fantastic development environment to make sure code flows safely and securely to production. Nothing particularly exotic but they help make the code readable and consistent across an ever growing engineering department. engineering infrastructure security

PHP 15

Hands-on Lessons for Advanced Topics in Entrepreneurship

Startup Lessons Learned

We wanted to give you a rundown of what’s in store, along with particular insight into two of the workshops we’re most excited to have lined up for Gold and VIP attendee s—one session with Jez Humble on implementing continuous delivery and one with Alistair Croll on Lean analytics for corporate entrepreneurs. To demonstrate the kind of thing we have in mind, we spoke to Jez Humble, who will lead a workshop, Continuous Delivery: Deploy Safer, Learn Faster.

Lean 23

Lessons Learned: Five Whys

Startup Lessons Learned

So, in the example above, wed have to take five corrective actions: bring the site back up remove the bad code help so-and-so understand why his code doesnt work as written train so-and-so in the principles of TDD change the new engineer orientation to include TDD I have come to believe that this technique should be used for all kinds of defects, not just site outages. By continuously adjusting, we eventually build up a robust series of defenses that prevent problems from happening.

Lean 47

Four myths about the Lean Startup

Startup Lessons Learned

And they can benefit from the speed and discipline of starting with a minimum viable product and then learning and iterating continuously. Many lean startups are ambitious and are able to deploy large amounts of capital. Case Study: Continuous deployment makes releases n.

Lean 43

Lessons Learned: The ABCDEF's of conducting a technical interview

Startup Lessons Learned

Finding great engineers is hard; figuring out whos good is even harder. For software engineers, I think this absolutely has to be a programming problem solved on a whiteboard. I have found this quite rare in engineers. Many of us engineers are strong introverts, without fantastic people skills. To test for empathy, I always make sure that engineers have one or two interviews with people of wildly different background, like a member of our production art department.

Lean 13

Translation Memory

Code as Craft

Since we are a company with a continuous deployment development process, we do this on a daily basis and as an result get a significant number of new messages to be translated along with changes or deletions of existing ones that have already been translated. Etsy’s Search Team has integrated Lucene / Solr into our deployment infrastructure allowing for Solr configuration, Java-based indexers, and query parsing logic to go to production code in minutes. By: Diego Alonso.

Lessons Learned: Work in small batches

Startup Lessons Learned

Lessons Learned by Eric Ries Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. Every time an engineer checks in code, they are batching up a certain amount of work. This is easiest to see in deployment.

Lean 36

Infrastructure upgrades with Chef

Code as Craft

In addition to our production infrastructure, every engineer and designer also have their own VM to develop on the Etsy stack (see this post for details). We have about 30 engineers regularly making changes to our cookbooks. For infrastructure changes we have the same continuous deployment mentality. continuously deployed. hide a change behind a rollout flag and makes it easier for engineers that are. engineering infrastructure operations

The Lean Entrepreneur is here

Startup Lessons Learned

PayPal, under the leadership of David Marcus and Bill Scott, re-defining and re-engineering itself by embracing Lean Startup to improve the product experience. My personal background was as an engineer and my companies had been Web-based startups, so that is what I wrote about.

Lean 60

Fear is the mind-killer

Startup Lessons Learned

I spent some time with his company before the conference and discussed ways to get started with continuous deployment , including my experience introducing it at IMVU. He summarized that conversation well, so rather than re-tread that material, Ill quote it here: One thing that I was surprised to learn was that IMVU started out with continuous deployment. Understanding these three factors makes it clear as to why continuous deployment was a starting point for IMVU.

Lessons Learned: What does a startup CTO actually do?

Startup Lessons Learned

So I initially gravitated to the CTO title, and not VP of Engineering. And what about if deployment takes forever? Some options can improve the performance of the softare at the expense of readability, deployability, or scalability.

CTO 61

Lessons Learned: The lean startup

Startup Lessons Learned

See Customer Development Engineering for my first stab at articulating the theory involved) Ferocious customer-centric rapid iteration, as exemplified by the Customer Development process. Since that time we've seen a massive change from product engineering to financial engineering. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

Lean 47

Lean Startup at Scale

Startup Lessons Learned

That is, once you’re no longer a small company and you have some success, how do you execute and continue to grow through innovation? We work in prototypically four-week iterations, with quality engineers and software developers working in close collaboration. Here''s the simplest form of that cycle: Week -1 - Planning/End-of-Cycle - Software engineers are planning: writing specifications, doing light prototyping, and experimentation.

Lean 40

Lessons Learned: The three drivers of growth for your business.

Startup Lessons Learned

I break the answer to that question down into three engines: Viral - this is the business model identified in the presentation as "Get Users." Thats why eBay advertises on search engines, and Facebook doesnt. Labels: search engine marketing 0comments: New comments are not allowed. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

Lean 43

Pivot, don't jump to a new vision

Startup Lessons Learned

As the CTO/VP Engineering, I was the worst offender. That means that I (and other engineers) were able to participate in the problem team discussions. Such discussions would have been impossible in our execution-oriented engineering team meetings. Most engineers naturally think about repurposing the technology platform, and this is a common pattern. As an engineer thinking of doing a startup applying Steven's approach, your teachings are pure gold!

Minimum Viable Product: a guide

Startup Lessons Learned

Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Lessons Learned by Eric Ries Monday, August 3, 2009 Minimum Viable Product: a guide One of the most important lean startup techniques is called the minimum viable product. Its power is matched only by the amount of confusion that it causes, because its actually quite hard to do.

Do lean startup principles have a place in the enterprise?

The Next Web

Editor’s Note: The following is a guest post by James Donelan , the VP of engineering at MuleSoft , provider of the world’s most widely used integration platform. Use a continuous delivery model to release new features quickly with the least amount of friction.

Lessons Learned: A new version of the Joel Test (draft)

Startup Lessons Learned

But if you want to practice rapid deployment, you need to be able to deploy that build in one step as well. If you want to do continuous deployment, youd better be able to certify that build too, which brings us to. Daily builds are giving way to true continuous integration, in which every checkin to the source control system is automatically run against the full battery of automated tests. For more on continuous deployment, see Just-in-time Scalability.

Lean 33

Moving Fast at Scale: the slides, and a reprise in NYC

Code as Craft

Continuous Deployment: The Why and the How (Kellan Elliott-McCrea, VP of Engineering). Deployinator: Turning THE FEAR into ‘the fear’ (Erik Kastner, Software Engineer, Developer Tools).

Chad 15

How Etsy Uses Code “Slush” to Manage Development During the Holidays

Code as Craft

Over the years, our product, engineering, and member-facing organizations have developed practices and approaches to support our community during the intensity of the holidays. Engineers went from deploying five times a day to once a day.

Chad 21

Teaching Testing: Our Testing 101 Materials

Code as Craft

Etsy engineers have a wide variety of backgrounds, strengths, and weaknesses, so there are no engineering skills we can take for granted. And there are things you can’t just assume engineers will learn for themselves because you throw a codebase and a workflow at them. To that end, I recently wrote two “Testing 101″ materials for use by all Etsy engineers.

PHP 5