Remove Continuous Deployment Remove Cost Remove Design Remove Development Team Review
article thumbnail

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. I dont think so.

article thumbnail

The Principles of Product Development Flow

Startup Lessons Learned

Reinertsen is keenly aware of what makes product development different from other business functions, like manufacturing, that we sometimes use as a metaphor. Product development deals in designs, which are fundamentally intangible. Today, only 2 percent of product developers measure queues. First, how big are our queues?

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Lessons Learned: What is customer development?

Startup Lessons Learned

You can learn about customer development, and quite a bit more, in Steves book The Four Steps to the Epiphany. This is a self-published book, originally designed as a companion to Steves class at Berkeleys Haas school of business. Our goal in product development is to find the minimum feature set required to get early customers.

article thumbnail

Lessons Learned: Product development leverage

Startup Lessons Learned

The idea of leverage is simple: for every ounce of effort your product development team puts into your product, find ways to magnify that effort by getting many other people to invest along with you. Making UGC work requires good tools, open standards, and proper incentive design. Its a key lean startup concept.

article thumbnail

Lessons Learned: The engineering manager's lament

Startup Lessons Learned

I now believe that the "pick two" concept is fundamentally flawed, and that lean startups can achieve all three simultaneously: quickly bring high-quality software to market at low cost. Thats why we need continuous integration and test-driven development. First of all, its a myth that cutting corners saves time.

article thumbnail

Lessons Learned: The hacker's lament

Startup Lessons Learned

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. But when there is a task half-done, its actually slowing the team down. Imagine a team working from a forced-rank priority queue.