Blog Books Continuous Deployment Development Team Review 
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. I owe it originally to lean manufacturing books like Lean Thinking and Toyota Production System. Take the example of a design team prepping mock-ups for their development team.
Startup Lessons Learned
NOVEMBER 8, 2008
This theory has become so influential that I have called it one of the three pillars of the lean startup - every bit as important as the changes in technology or the advent of agile development. You can learn about customer development, and quite a bit more, in Steves book The Four Steps to the Epiphany. Heres the catch.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
OCTOBER 20, 2008
TWO See page 199 of Poppendieck and Poppendiecks new(er) book for a finer analysis of defects and bugs: Unit tests prove that the code does what the developers want it to do, i.e. there are no defects. The PMs relationship to quality is a step removed from the development team that is directly affected by the quality every day.
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. Reinertsen is the book for you. What will this do?
Expert insights. Personalized for you.
161 
Let's personalize your content