Remove Cofounder Remove Continuous Deployment Remove Networking
article thumbnail

Why Continuous Deployment?

Startup Lessons Learned

Lessons Learned by Eric Ries Monday, June 15, 2009 Why Continuous Deployment? Of all the tactics I have advocated as part of the lean startup , none has provoked as many extreme reactions as continuous deployment , a process that allows companies to release software in minutes instead of days, weeks, or months.

article thumbnail

Amsterdam-based Rockstart Accelerator’s first graduates head to Silicon Valley

The Next Web

In all seriousness, the Q&A panel session will include European entrepreneurs like Guillaume Decugis, who sold Musiwave for $125 million and is currently co-founder and CEO of Scoop.it, and Unity Technologies co-founder and CEO David Helgason (read our interview with him ).

Insiders

Sign Up for our Newsletter

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

article thumbnail

Top 120 Startup Posts for 2010

SoCal CTO

November 23, 2010 Entrepreneurs, Using Outsourcing to Obtain Capital Efficiency Needs to be Thought Through to be Effective - Robert Ochtel , June 7, 2010 Teen Entrepreneur, Brian Wong, Youngest Founder to Receive Angel Funding - teenentrepreneurblog.com , October 28, 2010 Build Your Own Silicon Valley?

article thumbnail

Pivot, don't jump to a new vision

Startup Lessons Learned

Some startups fail because the founders cant have this conversation - they either blow up when they try, or they fail to change because they are afraid of conflict. We went through another pivot when we switched again from instant messaging to social networking. Thats why its so essential to have a co-equal problem team.

article thumbnail

Lessons Learned: The lean startup

Startup Lessons Learned

For example, one angel investor reportedly invested in several hundred social networking ventures employing this philosophy. Mark Montgomery Founder Kyield Initium VC September 12, 2009 4:21 AM Mark Montgomery said. Case Study: Continuous deployment makes releases n. Otherwise it's a great idea.

Lean 168
article thumbnail

Lessons Learned: Throwing away working code

Startup Lessons Learned

I was constantly coming up with arguments to save it: that we couldnt be sure that the feature wouldnt be useful later, that maybe some customers liked it even though most didnt, that it wasnt consistent with our company values to become a proprietary IM network. Case Study: Continuous deployment makes releases n.

article thumbnail

Lessons Learned: Customer Development Engineering

Startup Lessons Learned

Customers found it confusing and it turned out to be at odds with our fundamental value proposition (which really requires an independant IM network). Labels: agile , continuous deployment , customer development , events , listening to customers , slides 3comments: Sean Murphy said. Talk about waste.