Startup Lessons Learned

NOVEMBER 13, 2008

By continuously adjusting, we eventually build up a robust series of defenses that prevent problems from happening. This approach is a the heart of breaking down the "time/quality/cost pick two" paradox , because these small investments cause the team to go faster over time. Case Study: Continuous deployment makes releases n.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

SEPTEMBER 30, 2008

If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? Platform selection and technical design - if your business strategy is to create a low-burn, highly iterative lean startup, youd better be using foundational tools that make that easy rather than hard.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

NOVEMBER 7, 2008

We had endless arguments internally about what features it should include, how the avatars should look, and how much it should cost. Just load them all in and choose a low cost-per-click. Seems like a fairly low-cost method of gauging customer interest for a would-be product. Case Study: Continuous deployment makes releases n.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

SEPTEMBER 10, 2008

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. For more on continuous deployment, see Just-in-time Scalability. Can you make a build in one step?

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

NOVEMBER 14, 2013

Starting on the evening of December 11 and running through December 13—for VIP pass holders only—we’re partnering with UP Global’s Startup Weekend to offer a two-day Lean Startup immersion program , specially designed to teach you how to put Lean Startup theory directly into practice. Thus we reduce the risk of deployments.

Continuous Deployment 162

Continuous Deployment Norway Lean Analytics 162

Startup Lessons Learned

OCTOBER 11, 2010

I found the perfect person at the department of Industrial Design Engineering of the Delft University of Technology. New cheap flashable micro controllers make firmware updates possible for low cost hardware. Continuous deployment of hardware is an exciting new capability. It turned out we indeed could.

Continuous Deployment 164

Continuous Deployment Technical Cofounder Cofounder San Francisco 164

Startup Lessons Learned

SEPTEMBER 7, 2008

It seems many startups these days are under a lot of pressure to outsource their development organization to save costs. Labels: agile , continuous deployment , customer development , events , listening to customers , slides 3comments: Sean Murphy said. Case Study: Continuous deployment makes releases n.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

MARCH 25, 2010

for Harvard Business Review) Over at Harvard Business Review, Ive been building up a series designed to introduce the Lean Startup methodology to a business-focused audience. Case Study: Continuous deployment makes releases n. Lessons Learned by Eric Ries Thursday, March 25, 2010 Speed up or slow down? Are we going too fast?

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

SEPTEMBER 2, 2008

We wanted an agile approach that would allow us to build our software architecture as we needed it, without downtime, but also without large amounts of up-front cost. Labels: agile , continuous deployment 1 comments: timothyfitz said. Case Study: Continuous deployment makes releases n.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

MAY 9, 2012

Brant and Patrick have set out to write and design a book that not only describes practical steps for implementing Lean Startup principles in your innovative endeavors – but to inspire your creativity as well by sharing diverse examples of what works, and more importantly, what often doesn’t work. It will be published by Wiley this fall.

Entrepreneur 167

Entrepreneur Lean Southern California San Diego 167

Startup Lessons Learned

NOVEMBER 8, 2008

This is a self-published book, originally designed as a companion to Steves class at Berkeleys Haas school of business. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Heres the catch.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

JANUARY 19, 2009

Lessons Learned by Eric Ries Monday, January 19, 2009 Lean hiring tips In preparing for the strategy series panel this week, I have been doing some thinking about costs. I want to talk specifics, and when you come right down to it, most technology startups dont have a very interesting cost structure. The blog is fantastic as well.

Lean 140

Lean Hiring San Francisco Continuous Deployment 140

Startup Lessons Learned

SEPTEMBER 13, 2008

Since we were only paying per click, it didnt cost us anything to cast a wide net. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica. We tried obvious competitors as well as long-shots.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

DECEMBER 8, 2008

In this post I want to talk about the nuts and bolts of how to integrate continuous integration into your team, and how to use it to create two important feedback loops. First, a word about why continuous integration is so important. This will help me improving me my work skills in term of coding and designing.

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136

Startup Lessons Learned

JULY 2, 2009

Yet in every situation where I have asked, nobody has been tasked with making a realistic estimate, either of the impact of this lack of training or the real costs of the solution. Five Whys is designed to avoid these nebulous arguments. Remember that the cost of the solutions is proportional to the problem caused.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

FEBRUARY 28, 2009

Most of all, these arguments stemmed from a simple misconception: that the code we had written was an asset, and that it would cost us to throw it away. But code written that doesnt help the company succeed is a sunk cost. Case Study: Continuous deployment makes releases n. Expo (and a call for he.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

JUNE 17, 2010

The artists on the team had called in the big guns, and VP-level folks were there to explain the importance of certain aspects of the visual design that threatened to be cut. And lastly, it removes the engineering team’s ability to find breakthrough solutions that might deliver most of the value at a fraction of the cost.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

APRIL 29, 2013

Eric has talked often about recognizing a startup as an organization designed to create a new product or service under conditions of extreme uncertainty. Not to mention $200,000 in staff time and hard costs. Generously, it might cost you $20,000. In other words, you could test ten book ideas for the cost of publishing one.

Lean 165

Lean Technical Review Startup Software Review 165

Startup Lessons Learned

APRIL 9, 2009

And instead of design, engineering, QA, and operations we have a solution team implementing a startup-centric version of agile development. When people ask about how to reconcile metrics with interaction design, usability testing, or in-person customer interviews, this is the issue they are really talking about.

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

Startup Lessons Learned

NOVEMBER 4, 2008

Lean startups have the ability to use this commodity stack to lower costs and, more importantly, reduce time to market. The biggest source of cost/time advantage that all lean companies have is avoiding building features that customers dont want. Case Study: Continuous deployment makes releases n.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

MARCH 27, 2009

While some cost-cutting measures reduce that number, others increase it. In lean times, it’s most important to focus on cutting costs in ways that speed you up, not slow you down. Otherwise, cutting costs just leads to going out of business a little slower. Case Study: Continuous deployment makes releases n.

San Francisco 117

San Francisco Lean Continuous Deployment DC 117

Startup Lessons Learned

DECEMBER 14, 2009

I had a lot of use for this concept back when I worked on game design and virtual worlds. In order to maintain game play balance, game designers have to take into account the needs of customers who have an excess of four different assets: time , money , skill , and passion. Having a balanced ecosystem is what game designers strive for.

Customer 156

Customer San Francisco Viral Lean 156

Startup Lessons Learned

MARCH 29, 2010

Doesnt the communication overhead of a large team lead to chaos of overlapping experiments and continuously-deployed bugs?" "If If you just throw a minimum viable product out the door to see what sticks, wont that necessarily be ugly and badly designed? Is design important to lean startups? Is design important to lean startups?

San Francisco 120

San Francisco Lean Continuous Deployment DC 120

Startup Lessons Learned

JANUARY 2, 2010

The cost of creating new companies is falling rapidly, and access to markets, distribution, and information is within the reach of anyone with an internet connection. This is just like a startup to me, complete with distribution and product development challenges, ecosystem design and many, many customers.

San Francisco 122

San Francisco Lean Continuous Deployment DC 122

Startup Lessons Learned

MARCH 22, 2010

The cost of creating new companies is falling rapidly, and access to markets, distribution, and information is within the reach of anyone with an Internet connection. The cost will be felt in jobs -- thousands of new jobs that could have been created here, but werent. Case Study: Continuous deployment makes releases n.

San Francisco 121

San Francisco Indiana Lean Startup 121

Startup Lessons Learned

APRIL 14, 2009

Their product development team is hard at work on a next-generation product platform, which is designed to offer a new suite of products – but this effort is months behind schedule. And yet their numbers continue to grow, month after month. Our cost to acquire a customer on AdWords was only a few cents.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

FEBRUARY 9, 2009

The Lean Startup: a Disciplined Approach to Imagining, Designing, and Building New Products.: The Lean Startup is a practical approach for creating and managing a new breed of company that excels in low-cost experimentation, rapid iteration, and true customer insight. Case Study: Continuous deployment makes releases n.

Lean 68

Lean San Francisco Web Advisory Board 68

Startup Lessons Learned

OCTOBER 6, 2008

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. Thats what business is designed to do. How did they do it?

San Francisco 128

San Francisco Lean Continuous Deployment Agile 128

Startup Lessons Learned

JANUARY 4, 2009

This has two major drawbacks: the central directory can become a single point of failure, and there is a performance cost for having to consult the directory ever time you want to access data anywhere in the cluster. Sharding for startups To support a single partitioning scheme is easy, especially if you design for it from the start.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

FEBRUARY 11, 2009

Its obvious that can lower your development costs, but I think its even more important that it can reduce your time to market. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

Software Review 68

Software Review Software Hiring San Francisco 68

Startup Lessons Learned

JUNE 5, 2009

If it costs $0.10 to acquire an early adopter, how much should it cost to acquire a mainstream customer? Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. But $10.00?

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

DECEMBER 7, 2008

Even if, in a previous life, you were a world expert in some functional specialty, like in-depth market research or scalable systems design, the compressed timeline of a startup makes it irrelevant. These are two other Extreme Programming practices that are explicitly designed to counteract the problems inherent in this situation.

Software Review 94

Software Review Technical Review San Francisco Part-Time VPE 94

Startup Lessons Learned

AUGUST 24, 2009

As the costs of production fall, it’s getting easier and easier to send in a proposal or even a complete work. user-generated content) can increase liquidity and decrease distribution costs (notably talent search and evaluation), there are certain individuals whose opinions will count for more than the simple votes of the masses.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

APRIL 26, 2009

Plus, we saw some of the intrinsic limitations of supporting such a large staff: slower cycle times, higher cost basis, and - most importantly - the ability to serve only a limited number of customer segments. Making UGC work requires good tools, open standards, and proper incentive design. We didnt think wed able to compete with that.

Product Development 88

Product Development Developer San Francisco Product 88

Startup Lessons Learned

JULY 3, 2009

If your practice is not designed to cope with uncertainty, it has no place in a startup - even if your startup is located in government or enterprise. ericries #leanstartup Another new idea in the section on continuous deployment and the cluster immune system. Case Study: Continuous deployment makes releases n.

Lean 60

Lean San Francisco Continuous Deployment Cofounder 60

Startup Lessons Learned

SEPTEMBER 8, 2008

It cost us a few hundred thousand dollars to get our app up and running, but none of that was dollars spent on software licenses or professional services. I cant really imagine how much it cost our "grownup" counterparts at other dot-com startups to get their first app up and running. Case Study: Continuous deployment makes releases n.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

Startup Lessons Learned

SEPTEMBER 8, 2009

That is just currently a full personal money sucking process, as you're taxed on income and have no business breaks yet, besides supplies, the majority of costs to start up a business have no tax advantages to creating a start up. You can see the design of the program here. Case Study: Continuous deployment makes releases n.

DC 90

DC Washington San Francisco SBIR 90