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. Thats pretty clear.

Agile 111

Agile Customer Development Developer San Francisco 111

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.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

DECEMBER 14, 2017

Editor’s Note: We wrapped up the 2017 Lean Startup Week in San Francisco just a few weeks ago, and we’re excited to share with you some of the best lessons learned in entrepreneurship and corporate innovation. Instead, employees “were like, ‘Well, I don't know how to give my peer feedback. Second, don’t simply hire your buddies.

Lean 245

Lean Startup CTO Hire Cofounder 245

Startup Lessons Learned

DECEMBER 6, 2008

The advantages of cross-functional teams are well documented, and for a thorough treatment I recommend the theory in the second half of Agile Software Development with Scrum. Scrum recommends 30 days; I have worked in one or two-week cycles up to about three months. At IMVU, we found 60 days was just about right. Expo SF (May.

San Francisco 74

San Francisco SCRUM Lean Continuous Deployment 74