Continuous Deployment Development Team Review Founder Management 
Startup Lessons Learned
OCTOBER 5, 2008
Lessons Learned by Eric Ries Sunday, October 5, 2008 The product managers lament Life is not easy when youre working in an old-fashioned waterfall development process, no matter what role you play. The product manager was clearly struggling to get results from the rest of the team. Frustration is mounting.
Startup Lessons Learned
FEBRUARY 20, 2009
Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. Similar results apply in product management, design, testing, and even operations. Normally I focus on the techniques you need to reduce batch size, like continuous integration.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
OCTOBER 20, 2008
Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their product development process. This engineering manager is a smart guy, and very experienced.
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. Managing timelines instead of queues. Inflexibility.
Startup Lessons Learned
NOVEMBER 8, 2008
When creating a new market, expect to spend as long as two years before you manage to get traction with early customers, but enjoy the utter lack of competition. Our goal in product development is to find the minimum feature set required to get early customers. Instead, we do everything possible to validate the founders belief.
Startup Lessons Learned
NOVEMBER 17, 2008
Id like to talk about a technique Ive used to help manage this growth without slowing down. This technique rests on three things: identifying the kinds of work that need to get done, creating the right type of teams for each kind, and steering the company by allocating resources among them.
Startup Lessons Learned
JUNE 8, 2009
You constantly assess the situation, looking for hazards and timing your movements carefully to get across safely. So the product development team was busy creating lots of split-tests for lots of hypotheses. Each day, the analytics team would share a report with them that had the details of how each test was doing.
Expert insights. Personalized for you.
158 
Let's personalize your content