Remove Cost Remove Customer Development Remove Presentation Remove Software Review
article thumbnail

10,000 Startups – Startup Weekend Next

Steve Blank

The class teaches founders how to dramatically reduce their failure rate through the combination of business model design, customer development and agile development using the Startup Owners Manual. More importantly, it makes no demands of you to stand and deliver your weekly customer development progress in front of your peers.

Startup 335
article thumbnail

The free software hiring advantage

Startup Lessons Learned

Lessons Learned by Eric Ries Wednesday, February 11, 2009 The free software hiring advantage This is one of those startup tips Im a little reluctant to share, because its been such a powerful source of competitive advantage in the companies Ive worked with. Especially for a startup, not taking maximum advantage of free software is crazy.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Lessons Learned: A new version of the Joel Test (draft)

Startup Lessons Learned

I am convinced one of Joel Spolskys lasting contributions to the field of managing software teams will turn out to be the Joel Test , a checklist of 12 essential practices that you could use to rate the effectiveness of a software product development team. Do you fix bugs before writing code? Please leave feedback!)

article thumbnail

The Ultimate Guide to Starting a Software Company

Up and Running

Since the term “cloud computing” was coined in 1996—at least as we have come to understand its meaning—the software as a service industry has exploded. If you use software like LivePlan, you can create this initial “lean plan” in under an hour and then spend your time where it really matters—on validating your idea.

article thumbnail

Lessons Learned: Five Whys

Startup Lessons Learned

A new bit of code contained an infinite loop! why did that code get written? Hes a new employee, and he was not properly trained in TDD So far, this isnt much different from the kind of analysis any competent operations team would conduct for a site outage. Most engineers would ship code to production on their first day.

article thumbnail

Hacking for Defense @ Stanford – Weeks 8 and 9

Steve Blank

And they’re getting a handle on what it costs to build a company to deliver it. Because of the embedded presentations this post is best viewed on the website.). Next week the teams will present their final Lessons Learned presentations. Team Presentations: Weeks 8 and 9. This post is a continuation of the series.

article thumbnail

Lessons Learned: Continuous integration step-by-step

Startup Lessons Learned

Integration risk is the term I use to describe the costs of having code sitting on some, but not all, developers machines. It happens whenever youre writing code on your own machine, or you have a team working on a branch. It also happens whenever you have code that is checked-in, but not yet deployed anywhere.