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.

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.

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?"

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: Continuous deployment and continuous learning

Startup Lessons Learned

Lessons Learned by Eric Ries Tuesday, February 10, 2009 Continuous deployment and continuous learning At long last, some of the actual implementers of the advanced systems we built at IMVU for rapid deployment and rapid response are starting to write about it.

The Entrepreneur's Guide to Customer Development

Startup Lessons Learned

I believe it is the best introduction to Customer Development you can buy. As all of you know, Steve Blank is the progenitor of Customer Development and author of The Four Steps to the Epiphany. Here’s hoping they soon tackle Customer Validation.

Lessons Learned: What is customer development?

Startup Lessons Learned

Lessons Learned by Eric Ries Saturday, November 8, 2008 What is customer development? But too often when its time to think about customers, marketing, positioning, or PR, we delegate it to "marketroids" or "suits." They almost always fail for lack of customers.

Lessons Learned: Combining agile development with customer development

Startup Lessons Learned

Lessons Learned by Eric Ries Monday, March 16, 2009 Combining agile development with customer development Today I read an excellent blog post that I just had to share. In most agile development systems, there is a notion of the "product backlog" a prioritized list of what software is most valuable to be developed next. The breakthrough idea of agile is that software should be built iteratively, with the pieces that customers value most created first.

Agile 78

Founder personalities and the “first-class man” theory of management

Startup Lessons Learned

Lessons Learned by Eric Ries Friday, July 9, 2010 Founder personalities and the “first-class man&# theory of management At any given time, something like four percent of the US population is engaged in some form of new-company-creation. Case Study: Continuous deployment makes releases n.

Pivot, don't jump to a new vision

Startup Lessons Learned

Each has its own iterative process: customer development and agile development respectively. The hardest part of entrepreneurship is to develop the judgment to know when its time to change direction and when its time to stay the course. Some startups avoid getting customer feedback for precisely this reason: they are afraid that if early reactions are negative, theyll be "forced" to abandon their vision. IMVU had a roughly two-month-long development cycle.

Support the Startup Founders Visa with a tweet

Startup Lessons Learned

Lessons Learned by Eric Ries Saturday, September 19, 2009 Support the Startup Founders Visa with a tweet Its been an exhilarating first day here in Washington DC for the Geeks on a Plane tour. We can remedy it by creating a special visa for startup founders. Letting just 10,000 startup founders into the country each year could have a visible effect on the economy. Lets use 2gov.org to raise awareness of the Startup Founders Visa movement in congress.

Lessons Learned: When NOT to listen to your users; when NOT to.

Startup Lessons Learned

Lessons Learned by Eric Ries Monday, October 6, 2008 When NOT to listen to your users; when NOT to rely on split-tests There are three legs to the lean startup concept: agile product development , low-cost (fast to market) platforms , and rapid-iteration customer development. The most common need is becoming more customer-centric. They need to incorporate customer feedback into the product development and business planning process.

Lessons Learned: Getting started with split-testing

Startup Lessons Learned

Lessons Learned by Eric Ries Sunday, December 7, 2008 Getting started with split-testing One of the startup founders I work with asked me a smart question recently, and I thought Id share it. My favorite is to rearrange the steps of your registration process for new customers. If youre a founder or top-level executive, have the courage to be wrong in a very public way. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Announcing our investment in Dataloop

The Equity Kicker

Our other category of investment is ‘idea stage’, often with solo-founders.). We got to know David Gildeh, the CEO and one of three co-founders, around this time last year. We were encouraged by their progress so we dived in deep to develop our understanding of the market.

Cloud 109

Top 120 Startup Posts for 2010

SoCal CTO

500 Hats , January 10, 2010 Developing new startup ideas - Chris Dixon , March 14, 2010 Batch Processing Millions and Millions of Images - Code as Craft , July 9, 2010 jQuery Plugin: Give Your Characters a NobleCount - The Product Guy , March 23, 2010 How do the sample Series Seed financing documents differ from typical Series A financing documents? Some really great stuff in 2010 that aims to help startups around product, technology, business models, etc.

A large batch of videos, slides, and audio

Startup Lessons Learned

Or watch my full #leanstartup presentation at Seedcamp in London: And two bonus videos that are well worth watching (weally): Timothy Fitz, who worked for me at IMVU, giving an in-depth presentation on the details of the continuous deployment system that we built there.

Audio 122

Four myths about the Lean Startup

Startup Lessons Learned

That process involves rapid hypothesis testing, validated learning about customers , and a disciplined approach to product development. Truth: The Lean Startup methodology applies to all companies that face uncertainty about what customers will want.

Lean 168

Sneak preview, Grockit

Startup Lessons Learned

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Lo, my 57692 subscribers, who are you?

Startup Lessons Learned

I did it originally as a demonstration of the advantages of having a pathetically small number of customers , but I found the actual info so incredibly helpful, I have done it several times since. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Interviews

Startup Lessons Learned

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Six streaming locations

Startup Lessons Learned

Well continue to post links to new events to the conference website as we get them confirmed. Well continue to post links to new events to the conference website as we get them confirmed. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Lessons Learned: What does a startup CTO actually do?

Startup Lessons Learned

When Ive asked mentors of mine who have worked in big companies about the role of the CTO, they usually talk about the importance of being the external face of the companys technology platform; an evangelist to developers, customers, and employees.

CTO 171

A new field guide for entrepreneurs of all stripes

Startup Lessons Learned

TLDR: Brant Cooper and Patrick Vlaskovits , authors of The Entrepreneur's Guide to Customer Development are back with a new book called The Lean Entrepreneur. It took the idea of Customer Development and made it accessible to a whole new audience.

Lean 165

Videos galore

Startup Lessons Learned

The first is my talk on engagement loops and the levers of engagement from the Kontagent/Facebook Developer Garage. Customer Development at Startup2Startup Thanks for watching! The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Video 116

Kent Beck keynote, "To Agility, and Beyond"

Startup Lessons Learned

Kent is a significant figure in the field of software development. Kent is a significant figure in the field of software development. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Agile 110

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.

Philosophy Helps Start-Ups Move Faster (WSJ on the Lean Startup)

Startup Lessons Learned

Mr. Riess Lean Startup philosophy aims to help new companies make speedier decisions by taking a more disciplined approach to testing products and ideas and using the resulting customer feedback. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Lean 135

The Five Whys for Startups (for Harvard Business Review)

Startup Lessons Learned

Lessons Learned by Eric Ries Wednesday, June 2, 2010 The Five Whys for Startups (for Harvard Business Review) I continue my series for Harvard Business Review with the Lean Startup technique called Five Whys. Case Study: Continuous deployment makes releases n.

The Lean Startup Intensive is tomorrow at Web 2.0 Expo

Startup Lessons Learned

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Lean 115

Video update on the Startup Visa Act

Startup Lessons Learned

Lessons Learned by Eric Ries Thursday, April 29, 2010 Video update on the Startup Visa Act The Startup Visa Act continues to gain momentum on Capitol Hill, thanks to grassroots support of all of you. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Video 129

Speed up or slow down? (for Harvard Business Review)

Startup Lessons Learned

This is the first post that moves into making specific process recommendations for product development. Defective prototype code was as often thrown out (because customers didnt want it) as it was fixed (when customers did). Labels: product development Speed up or slow down?

Startup Visa update

Startup Lessons Learned

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

DC 124

For Startups, How Much Process Is Too Much? (for Harvard Business.

Startup Lessons Learned

The Conversation - Harvard Business Review : Still, startups develop some kind of process — whether its disciplined, haphazard, bureaucratic or empowering — because building a great product depends on it. Case Study: Continuous deployment makes releases n.

The Lean Startup Bundle

Startup Lessons Learned

Its a strange thing, to be asked by a potential customer if they can give you copious amounts of money, and then to have to refuse. It is the ultimate product development get-started guide to Lean Startup. It is the ultimate product development get-started guide to Lean Startup.

Lean 135

Two new scholarship programs for lean startups

Startup Lessons Learned

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Sneak preview, KISSmetrics (and more)

Startup Lessons Learned

Conference updates continue to pour in: Want to see more preview videos? Our sponsors continue to support the conference as well as deserving entrepreneurs. Conference updates continue to pour in: Want to see more preview videos?

Case Study: SlideShare goes freemium

Startup Lessons Learned

It requires separating the product launch from the marketing launch (see Dont Launch ) as well as other staple Lean Startup tactics: minimum viable product, split-testing, customer development and the pivot. Early this year, SlideShare launched custom channels.

Lean Startup fbFund slides and video

Startup Lessons Learned

Im currently working on doing video tutorials for technophobes, and while i understand the value of customer feedback, would charging from day one still apply? The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

Video 119

Case Study: kaChing, Anatomy of a Pivot

Startup Lessons Learned

If you havent seen it, Pascals recent presentation on continuous deployment is a must-see; slides are here. kaChing deployed the game across a slew of platforms, including MySpace, the iPhone, and the Yahoo App Platform. in fact only five people converted into paying customers.

Lessons Learned: The lean startup

Startup Lessons Learned

But by taking advantage of open source, agile software, and iterative development, lean startups can operate with much less waste. I am heavily indebted to earlier theorists, and highly recommend the books Lean Thinking and Lean Software Development. The application of agile development methodologies which dramatically reduce waste and unlock creativity in product development. Labels: customer development , lean startup 8comments: Amy said.

Lean 131

Lessons Learned: Five Whys

Startup Lessons Learned

By continuously adjusting, we eventually build up a robust series of defenses that prevent problems from happening. We had made so many improvements to our tools and processes for deployment, that it was pretty hard to take the site down. 100% of those tests ran, via a continuous integration cluster, after every checkin. When a test failed, it would prevent that revision from being deployed. This would deploy the change incrementally, one machine at a time.

Lessons Learned: The lean startup at UC Berkeley Haas School of.

Startup Lessons Learned

I liked the flattering Venture Hacks commentary so much Ill just quote it: Many founders believe that early stage startups are endeavors of execution. The customer is known, the product is known, and all we have to do is act. Case Study: Continuous deployment makes releases n.

Lessons Learned: Just-In-Time Scalability

Startup Lessons Learned

After all, the worst kind of waste in software development is code to support a use case that never materializes. Scalable systems are no exception - if your assumptions about how many customers youll have, or how they will behave are just a little bit wrong, you can wind up with a massive amount of wasted code. Labels: agile , continuous deployment 1 comments: timothyfitz said. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?