Customer Development Development Team Review Metrics Software 
Startup Lessons Learned
NOVEMBER 8, 2008
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. But too often when its time to think about customers, marketing, positioning, or PR, we delegate it to "marketroids" or "suits." This is a common mistake.
Startup Lessons Learned
FEBRUARY 20, 2009
Lessons Learned by Eric Ries Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. The batch size is the unit at which work-products move between stages in a development process. For software, the easiest batch to see is code. I dont think so.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
OCTOBER 5, 2008
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.
Startup Lessons Learned
OCTOBER 20, 2008
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.
Startup Lessons Learned
APRIL 26, 2009
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.
Startup Lessons Learned
OCTOBER 16, 2013
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.
Startup Lessons Learned
NOVEMBER 29, 2008
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.
Expert insights. Personalized for you.
168 
Let's personalize your content