Customer Development Programming SCRUM 
Startup Lessons Learned
MARCH 16, 2009
Lessons Learned by Eric Ries Monday, March 16, 2009 Combining agile development with customer development Today I read an excellent blog post that I just had to share. In most agile development systems, there is a notion of the "product backlog" a prioritized list of what software is most valuable to be developed next.
Startup Lessons Learned
SEPTEMBER 15, 2008
I am heavily indebted to earlier theorists, and highly recommend the books Lean Thinking and Lean Software Development. I also owe a great debt to Kent Beck, whose Extreme Programming Explained: Embrace Change was my first introduction to this kind of thinking. (So Labels: customer development , lean startup 8comments: Amy said.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
OCTOBER 5, 2008
Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more. But first I think we need to save the product manager from that special form of torture only a waterfall product development team can create. No departments The Five Whys for Startups (for Harvard Business R.
Startup Lessons Learned
SEPTEMBER 10, 2008
There are several ways to make progress evident - the Scrum team model is my current favorite. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? When its receding, we rescope. Do you have a spec? I think the new question needs to be "does the team have a clear objective?"
Startup Lessons Learned
APRIL 9, 2009
Thats the essence of so many of the lean startup techniques Ive evangelized: customer development , the Ideas/Code/Data feedback loop , and the adaptation of agile development to the startup experience. Creating a company-wide feedback loop that incorporates both customer development and agile development is a challenge.
Startup Lessons Learned
DECEMBER 6, 2008
When youve mastered that, consider adding operations, customer service, marketing, product management, business development - the idea is that when the team needs to get approval or support from another department, they already have an "insider" who can make it happen. At IMVU, we found 60 days was just about right.
Startup Lessons Learned
JULY 29, 2009
The Extreme Programming folks call those "spikes", and generally don't check them in.) Darn good - I have struggled in relevant conversations with our in house move to scrum/agile. Are the engineers in the customer development team allowed to push quick and dirty "prototypes" to production?
Expert insights. Personalized for you.
111 
Let's personalize your content