2008 SCRUM Software Development 
Startup Lessons Learned
SEPTEMBER 15, 2008
Lessons Learned by Eric Ries Monday, September 8, 2008 The lean startup Ive been thinking for some time about a term that could encapsulate trends that are changing the startup landscape. But by taking advantage of open source, agile software, and iterative development, lean startups can operate with much less waste.
Startup Lessons Learned
MARCH 16, 2009
XP and Scrum don’t have much to say - they punt. Ever since that time, I have struggled to explain how the feedback loop in customer development should interface with the feedback loop in product development. What causes projects like this to fail in traditional software development is that the solution is unknown.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Feld Thoughts
MAY 28, 2015
For example, from a post in 2008 about Rally’s $16.85m financing , I riffed on the origins of the company. I remember my friend Ryan Martens sitting down with me and Chris Wand around 2001 and walking us through his idea for changing the how he approached managing the software development process.
Startup Lessons Learned
DECEMBER 6, 2008
Lessons Learned by Eric Ries Saturday, December 6, 2008 The four kinds of work, and how to get them done: part three Those startups that manage to build a product people want have to deal with the consequences of that success. Scrum recommends 30 days; I have worked in one or two-week cycles up to about three months.
ctotodevelopers.blogspot.com
JULY 11, 2012
I cover several topics including agile software development, software startups, web 2.0, Labels: about me , agile planning , agile software development , cio , innovation , it management , organizational change , product management , project management , software development , software qa.
Expert insights. Personalized for you.
168 
Let's personalize your content