Remove Continuous Deployment Remove Development Team Review Remove Software
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. This is easiest to see in deployment.

article thumbnail

Lean Startup at Scale

Startup Lessons Learned

We work in prototypically four-week iterations, with quality engineers and software developers working in close collaboration. This finally bit us after a four month stint of development blew through its testing schedule by a factor of four: two scheduled weeks turned into two months before the product reached stability.

Lean 167
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: The product manager's lament

Startup Lessons Learned

I met one recently that is working on a really innovative product, and the stories I heard from their development team made me want to cringe. The product manager was clearly struggling to get results from the rest of the team. Labels: product development 8comments: Vincent van Wylick said.

article thumbnail

Lessons Learned: What is customer development?

Startup Lessons Learned

Lessons Learned by Eric Ries Saturday, November 8, 2008 What is customer development? For software, we have many - you can enjoy a nice long list on Wikipedia. Our goal in product development is to find the minimum feature set required to get early customers. Case Study: Continuous deployment makes releases n.

article thumbnail

Lessons Learned: The engineering manager's lament

Startup Lessons Learned

They just assumed it was the way software companies worked. In teams that follow the "pick two" agenda, which two has to be resolved via a power play. Unfortunately, threats work a lot better at incentivizing people to CYA than getting them to write quality software. I couldnt see that we were managing to pick even one.

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. So we tried to craft a strategy that would give us the product development leverage we needed to serve all customers.

article thumbnail

Lessons Learned: The hacker's lament

Startup Lessons Learned

Sometimes, a great hacker has the potential to grow into the CTO of a company, and in those cases all you need is an outside mentor who can work with them to develop those skills. At the end of the day, the product development team of a startup (large or small) is a service organization. I am basically a one-man shop.