Remove Continuous Deployment Remove Development Team Review Remove Lean Remove Software
article thumbnail

Lean Startup at Scale

Startup Lessons Learned

Guest post by Lisa Regan, writer for The Lean Startup Conference. As Lean Startup methods have been used now for a number of years, we’ve become increasingly interested in how companies use them to sustain growth. Next Tuesday, October 22 at 10a PT, we’ll take a look at this advanced entrepreneurship question.

Lean 167
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.

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. Expo SF (May.

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. Steve Blank has devoted many years now to trying to answer that question, with a theory he calls Customer Development. The Lean Startup Intensive is tomorrow at Web 2.0.

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: The ABCDEF's of conducting a technical interview

Startup Lessons Learned

The technical interview is at the heart of these challenges when building a product development team, and so I thought it deserved an entire post on its own. For software engineers, I think this absolutely has to be a programming problem solved on a whiteboard. Still, a startup product development team is a service organization.

article thumbnail

Lessons Learned: The hacker's lament

Startup Lessons Learned

When I get involved in companies that struggle with this problem, here is the kind of advice I think can help: Introduce TDD and continuous integration. This is one of the bedrock practices of any lean startup , and so its a common piece of advice I give out. However, its particularly helpful in this situation.