Agile Customer Development 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. Jim Murphy is a long-time agile practitioner in startups. But startups sometimes have trouble applying agile successfully. Enter Jims post.
Startup Lessons Learned
SEPTEMBER 15, 2008
But by taking advantage of open source, agile software, and iterative development, lean startups can operate with much less waste. I am heavily indebted to earlier theorists, and highly recommend the books Lean Thinking and Lean Software Development. 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
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. April 21 - Agile Vancouver is sold-out (thank you all so much!). The Lean Startup at Web 2.0 Expo, never fear.
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. Expo SF (May.
Steve Blank
MARCH 2, 2013
By Tuesday morning, students fleshed out what they believed to be their value proposition and customer segments. Scrum boards went up detailing everything they needed to accomplish by Friday afternoon. Tuesday afternoon they got out of the building and headed to a local mall to begin the customer validation and development process.
Startup Lessons Learned
SEPTEMBER 10, 2008
I know plenty of people who prefer more advanced source control system, but my belief is that many agile practices diminish the importance of advanced features like branching. Its not that the idea behind them is wrong, but I think agile team-building practices make scheduling per se much less important. Youd better. Expo SF (May.
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. October 6, 2008 12:17 AM r& said. Expo SF (May.
Expert insights. Personalized for you.
111 
Let's personalize your content