Customer Development Engineer Founder 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
The application of agile development methodologies which dramatically reduce waste and unlock creativity in product development. See Customer Development Engineering for my first stab at articulating the theory involved) Ferocious customer-centric rapid iteration, as exemplified by the Customer Development process.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
steveblank.com
JULY 8, 2011
AgileZen – project management visually see and interact with your work Kanbanery – Simple online team or personal kanban board LeanKit Kanban – Great for visualizing work of product development Kanban Pad – “Nice and lean” and free online Kanban tool Banana Scrum – A tool simple as Scrum itself.
David Teten
OCTOBER 1, 2015
What are the terms of their relationship with the founder? I’ve also asked this question on Quora.There, I ask for advice on how to best structure this for all parties: The development shop, the founders (outside of the dev shop), and potential outside investors. What are the timelines? The discounts? The cliffs? The fine print?
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. No engineering team. When we lose sight of the humanity of our customers, were not likely to be able to delight them.
Startup Lessons Learned
SEPTEMBER 10, 2008
At IMVU , our engineering team accumulated thousands upon thousands of tests, and we had a build cluster (using BuildBot ) that ran them. There are several ways to make progress evident - the Scrum team model is my current favorite. At IMVU, our rule was that a new engineer needed to push code to production on their first day.
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.
Expert insights. Personalized for you.
111 
Let's personalize your content