Startup Lessons Learned

SEPTEMBER 15, 2008

April 27, 2009 8:59 AM Anonymoussaid. July 15, 2009 11:18 PM markmontgomery said. Mark Montgomery Founder Kyield Initium VC September 12, 2009 4:21 AM Mark Montgomery said. Case Study: Continuous deployment makes releases n. First timers have insecurities and fears that prevent them from Focusing.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Startup Lessons Learned

MAY 7, 2009

Lessons Learned by Eric Ries Thursday, May 7, 2009 Fear is the mind-killer Fear is an emotion that slows teams down. I spent some time with his company before the conference and discussed ways to get started with continuous deployment , including my experience introducing it at IMVU. It makes us more cautious.

San Francisco 131

San Francisco Continuous Deployment Software Review Lean 131

Startup Lessons Learned

NOVEMBER 13, 2008

It seems your cluster architecture is one of the key architectural constraints making continuous deployment possible. If you cant deploy to 5% of the nodes and check the results, then how would you accomplish continuous deployment? February 11, 2009 8:05 AM Anonymoussaid. June 15, 2009 9:27 PM Mark Graban said.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

SEPTEMBER 30, 2008

So what does CTO mean, besides just "technical founder who really cant manage anyone?" January 18, 2009 8:22 AM Dan Khan said. Cheers, -Dan January 18, 2009 9:04 PM Ivo said. January 20, 2009 1:12 PM Anonymoussaid. April 12, 2009 12:28 AM kenshin said. April 21, 2009 4:51 PM Geethan said. Great article!

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

JULY 28, 2010

If you havent seen it, Pascals recent presentation on continuous deployment is a must-see; slides are here. the version that would facilitate the investment of real money) was planned for late-2009. Andy Mathieson, a founder and managing member at Fairview Capital , was particularly supportive. The result? The result?

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

Startup Lessons Learned

NOVEMBER 7, 2008

February 7, 2009 5:40 AM Major_Grooves said. May 6, 2009 3:03 PM Ivan Acosta-Rubio said. June 22, 2009 6:30 AM Anonymoussaid. June 28, 2009 2:51 PM beorn said. Case Study: Continuous deployment makes releases n. Otherwise they just canceled the orders with some excuse. Great post - I think Ill try this.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

NOVEMBER 8, 2008

Instead, we do everything possible to validate the founders belief. Most people cant sustain more than a few of these iterations, and the founders rarely get to be involved in the later tries. March 14, 2009 8:34 AM Can Sar said. April 11, 2009 1:22 AM CeeTee said. The root of that mistake is premature execution.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

SEPTEMBER 10, 2008

But if you want to practice rapid deployment, you need to be able to deploy that build in one step as well. If you want to do continuous deployment, youd better be able to certify that build too, which brings us to. For more on continuous deployment, see Just-in-time Scalability. May 15, 2009 1:17 AM neocoder said.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

SEPTEMBER 7, 2008

Labels: agile , continuous deployment , customer development , events , listening to customers , slides 3comments: Sean Murphy said. ► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

OCTOBER 5, 2008

If the team is continually falling behind, it would seem that these teams were no fully aware of their expectations to begin with. ► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

SEPTEMBER 15, 2008

It was actually my co-founder Will Harvey who taught me to present this data in the simple format weve discussed in this post. March 26, 2009 6:15 PM Will said. Case Study: Continuous deployment makes releases n. Thanks for the inspiration (and the slurpee)! Two Ways to Hold Entrepreneurs Accountable (for Ha.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

FEBRUARY 22, 2009

Lessons Learned by Eric Ries Sunday, February 22, 2009 Please teach kids programming, Mr. President Of course, what I really mean is: let them teach themselves. Then you set up a web app to co-ordinate volunteers who can wipe a hard drive and install Ubuntu. February 22, 2009 5:54 PM CapnCleaver said. Ill explain in a moment.

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

JULY 29, 2009

Lessons Learned by Eric Ries Wednesday, July 29, 2009 Embrace technical debt Financial debt plays an important and positive role in our economy under normal conditions. Very much appreciate the suggested solutions (Five Why's, split testing etc) July 29, 2009 6:24 AM Kevin Gadd said. July 29, 2009 6:57 AM Heiner Wolf said.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

JULY 2, 2009

Lessons Learned by Eric Ries Thursday, July 2, 2009 How to conduct a Five Whys root cause analysis In the lean startup workshops , we’ve spent a lot of time discussing the technique of Five Whys. "Problems are caused by insufficiently robust symptoms" symptoms => systems July 3, 2009 12:29 AM Daniel Tenner said.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

APRIL 4, 2010

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Case Study: Continuous deployment makes releases n. No departments The Five Whys for Startups (for Harvard Business R.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Startup Lessons Learned

SEPTEMBER 13, 2008

Thank yo u January 3, 2009 4:07 PM BillSeitz said. May 8, 2009 2:27 PM Eric said. May 8, 2009 2:39 PM VictusFate said. ► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

DECEMBER 16, 2009

Lessons Learned by Eric Ries Wednesday, December 16, 2009 What is Lean about the Lean Startup? Those who are interested in work-in-process might want to take a look at Work in small batches and Continuous deployment - Eric) Some specific TPS practices appear in Lean Startups. Case Study: Continuous deployment makes releases n.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

Startup Lessons Learned

MARCH 3, 2009

Lessons Learned by Eric Ries Tuesday, March 3, 2009 Employees should be masters of their own time Every startup should have a culture of learning. March 3, 2009 9:54 PM surya said. March 3, 2009 10:02 PM Sean Murphy said. March 3, 2009 11:15 PM kareem said. March 3, 2009 11:28 PM Jon said. Dont even go there.

Employee 146

Employee San Francisco Lean Software Review 146

Startup Lessons Learned

SEPTEMBER 2, 2008

Labels: agile , continuous deployment 1 comments: timothyfitz said. ► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Case Study: Continuous deployment makes releases n.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

APRIL 14, 2009

Lessons Learned by Eric Ries Tuesday, April 14, 2009 Validated learning about customers Would you rather have $30,000 or $1 million in revenues for your startup? It should be even more important to the founders themselves, because it demonstrates that their business hypothesis is grounded in reality. But all things are never equal. (Of

Customer 167

Customer San Francisco Lean Hockey Stick 167

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. March 16, 2009 11:18 PM William Pietri said. March 17, 2009 9:21 AM Eric said. March 17, 2009 9:39 AM Mike Tobias said. Just a thought.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

APRIL 9, 2009

Lessons Learned by Eric Ries Thursday, April 9, 2009 Built to learn Its been an exhilarating ride since the Web 2.0 sachinrekhi : "Visionary customers are as smart if not smarter then the founders" #leanstartup Theres no skipping the chasm. Ill continue to post about additional events as I get them scheduled. Expo last week.

San Francisco 132

San Francisco Continuous Deployment Lean Agile 132

Startup Lessons Learned

SEPTEMBER 2, 2008

Were trying to put some of these "its the system, stupid" ideas into practice on NileGuide (www.nileguide.com) April 28, 2009 9:19 PM Jake Faris said. September 3, 2009 12:25 PM Omar Ead said. Case Study: Continuous deployment makes releases n. Great points Eric. Another OODA loop fan!

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

FEBRUARY 28, 2009

Lessons Learned by Eric Ries Saturday, February 28, 2009 Throwing away working code Lean startups work by systematically eradicating waste. Luckily for me, my co-founders eventually prevailed and we went on to build a product that customers actually wanted. March 2, 2009 1:58 PM programiTV said. Thanks for sharing.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

AUGUST 26, 2009

Lessons Learned by Eric Ries Wednesday, August 26, 2009 Building a new startup hub Last week, I had a unique opportunity to spend some time in Boulder at the behest of TechStars. Inspiring ideas: real-time biz metrics; safe continuous deployment; A/B split testing. August 28, 2009 1:15 PM Derek Scruggs said.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

JUNE 2, 2010

As start-ups scale, this agility will be lost unless the founders maintain a consistent investment in that discipline. As start-ups scale, this agility will be lost unless the founders maintain a consistent investment in that discipline. Case Study: Continuous deployment makes releases n.

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

MARCH 25, 2010

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Case Study: Continuous deployment makes releases n. No departments The Five Whys for Startups (for Harvard Business R.

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

JULY 5, 2010

I have personally sold many copies of his book, and continue to recommend it as one of the most important books a startup founder can read. I have personally sold many copies of his book, and continue to recommend it as one of the most important books a startup founder can read. Take a look and let me know what you think.

Customer Development 166

Customer Development Developer San Francisco Customer 166

Startup Lessons Learned

DECEMBER 8, 2008

► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Case Study: Continuous deployment makes releases n. No departments The Five Whys for Startups (for Harvard Business R.

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136

Startup Lessons Learned

JANUARY 12, 2010

Some of my favorites: Ash Maurya (whose Achieving Flow in a Lean Startup was one of my favorite posts of 2009), Brant Cooper , CindyAlvarez , Laura Klein , Kevin Dewalt , Giff Constable - and I must be missing many more. Case Study: Continuous deployment makes releases n. Have a favorite who I overlooked?

Lean 146

Lean San Francisco Wiki Startup 146

Startup Lessons Learned

JULY 9, 2010

Lessons Learned by Eric Ries Friday, July 9, 2010 Founder personalities and the “first-class man&# theory of management At any given time, something like four percent of the US population is engaged in some form of new-company-creation. Case Study: Continuous deployment makes releases n. Are we solving the right problem?

San Francisco 161

San Francisco Management Founder Lean 161

Startup Lessons Learned

SEPTEMBER 14, 2008

Today, when I talk to startup founders, the most common answer I get to the question "do you talk to your customers?" September 25, 2009 5:23 PM jchunter said. Case Study: Continuous deployment makes releases n. Most of the people building our product werent themselves target customers.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Lessons Learned

JANUARY 19, 2009

Lessons Learned by Eric Ries Monday, January 19, 2009 Lean hiring tips In preparing for the strategy series panel this week, I have been doing some thinking about costs. Returning to our example of the beleaguered founder who still has the pager, before hiring an operations guy, try promoting someone from within to take on the job.

Lean 140

Lean Hiring San Francisco Continuous Deployment 140

Startup Lessons Learned

MAY 31, 2010

I am grateful to everyone who helped make this event a success, especially my co-organizers Charles Hudson and David Sachs. I am grateful to everyone who helped make this event a success, especially my co-organizers Charles Hudson and David Sachs. Case Study: Continuous deployment makes releases n.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

NOVEMBER 4, 2008

February 13, 2009 4:05 AM Eric said. Try this download link February 16, 2009 9:21 PM Anonymoussaid. March 29, 2009 9:05 PM Pierre-Olivier Charlebois said. Case Study: Continuous deployment makes releases n. Fantastic post with lots of value. Keep posting and thank you! Take a look and let me know what you think.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

FEBRUARY 22, 2010

One last suggestion, which is a technique I learned from my IMVU co-founder Will Harvey. One last suggestion, which is a technique I learned from my IMVU co-founder Will Harvey. Case Study: Continuous deployment makes releases n. No departments The Five Whys for Startups (for Harvard Business R.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

Startup Lessons Learned

DECEMBER 23, 2009

Lessons Learned by Eric Ries Wednesday, December 23, 2009 Why vanity metrics are dangerous In a previous post, I defined two kinds of metrics: vanity metrics and actionable metrics. Case Study: Continuous deployment makes releases n. In this post, Id like to talk about the perils of vanity metrics.

Metrics 167

Metrics San Francisco Lean Continuous Deployment 167