Startup Lessons Learned

NOVEMBER 8, 2008

Lessons Learned by Eric Ries Saturday, November 8, 2008 What is customer development? But too often when its time to think about customers, marketing, positioning, or PR, we delegate it to "marketroids" or "suits." Many of us are not accustomed to thinking about markets or customers in a disciplined way.

Customer Development 168

Customer Development Developer San Francisco Customer 168

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. Take the example of a design team prepping mock-ups for their development team. Give the dev team your very first sketches and let them get started.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

JULY 13, 2009

Lessons Learned by Eric Ries Monday, July 13, 2009 The Principles of Product Development Flow If youve ever wondered why agile or lean development techniques work, The Principles of Product Development Flow: Second Generation Lean Product Development by Donald G. Wow, great review! You just got burned!

Product Development 153

Product Development Developer San Francisco Product 153

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.

San Francisco 158

San Francisco Management Software Review Product 158

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. Still, a startup product development team is a service organization. Were there to serve customers direclty, as well as all of the other functions of the company.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

OCTOBER 20, 2008

Most of the other processs changes - mandatory design reviews (prelimninary, critical, etc), - documenting all our procedures, and so on - were to support those two factors. A project usually has an absolute duration and budget whereas the time and money dedicated to development within the project is where the tradeoffs are made.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

NOVEMBER 17, 2008

Now its time to start to think seriously about how to find a repeatable and scalable sales process, how to position and market the product, and how to build a product development team that can turn an early product into a Whole Product. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

San Francisco 88

San Francisco Lean Continuous Deployment DC 88