Startup Lessons Learned

JUNE 17, 2010

But according to the theory, this should have been covered by the various specs and documentation we were rigorous about producing. Instead, we spent time making sure the exact behavior of the tools were well documented – by engineers, naturally. Case Study: Continuous deployment makes releases n. Expo SF (May.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

JULY 3, 2009

The Lean Startup fbFund Edition View more documents from Eric Ries. davemcclure : amazing concepts on Continuous Development => "Cluster Immune System" @EricRies #LeanStartup @fbFund [link] dalelarson : Because most features take longer to argue and prioritize than to build. Case Study: Continuous deployment makes releases n.

Lean 60

Lean San Francisco Continuous Deployment Cofounder 60

Startup Lessons Learned

AUGUST 8, 2009

We owe a lot to this seminal document. Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? Case Study: Continuous deployment makes releases n. Expo SF (May.

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

FEBRUARY 7, 2013

Telecom O2 learning to move at the speed of the internet 500 Startups and their accelerated feedback loops on what works, and what doesn't work in early-stage investing. We stand on the shoulders of giants: customer development, the theory of disruptive innovation, the technology life-cycle adoption theory, and agile development.

Lean 167

Lean Entrepreneur Agile San Francisco 167

Startup Lessons Learned

NOVEMBER 5, 2008

Education Guideline Book (1st Edition) Sep 2006 View SlideShare document or Upload your own. Kent Beck keynote, "To Agility, and Beyond" Six streaming locations Interviews ► March (7) New conference website, speakers, agenda Two new scholarship programs for lean startups Speed up or slow down? 1 comments: Desoja said.

Advertising 60

Advertising San Francisco Media Continuous Deployment 60

Startup Lessons Learned

AUGUST 16, 2010

Designed for large businesses, the channels let a company share several types of documents, brand the channel with their own design elements, and then include display advertising, contest promotions, blog aggregation, social media integration and metrics reporting. Case Study: Continuous deployment makes releases n.

San Francisco 167

San Francisco Lean Analytics Continuous Deployment 167

Startup Lessons Learned

NOVEMBER 13, 2008

Each five whys email is a teaching document. We had made so many improvements to our tools and processes for deployment, that it was pretty hard to take the site down. Wed never heard of five whys, and we had plenty of "agile skeptics" on the team. Case Study: Continuous deployment makes releases n. Expo SF (May.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

MARCH 27, 2009

In fact, every single lean transformation documented in books like Lean Thinking took place in the midst of serious external threats. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

San Francisco 117

San Francisco Lean Continuous Deployment DC 117

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. Case Study: Continuous deployment makes releases n. I want to focus here on one particular strength: the ability to operate semi-autonomously.

San Francisco 74

San Francisco SCRUM Lean Continuous Deployment 74

Startup Lessons Learned

APRIL 7, 2010

I’ve previously documented that early-on in IMVU’s life, we made the mistake of building an IM add-on product instead of a standalone network. I’ve previously documented that early-on in IMVU’s life, we made the mistake of building an IM add-on product instead of a standalone network. Let me illustrate.

San Francisco 154

San Francisco Lean Metrics Design 154

Startup Lessons Learned

JANUARY 12, 2009

And I think a bad choice, a bad library, a horrible API, lack of documentation etc. You forgot to mention how awesome the documentation on php.net is. There are also a host of community sites dedicated to perl, and equally as many for the other prominent internet languages. Case Study: Continuous deployment makes releases n.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

SEPTEMBER 11, 2009

To imagine that this person does so only to get attention, or only to harass others, or only to harass you are to play into the hands of this geek autocracy on the Internet that just isn't viable anymore. However, you have opened yourself onto the internet with some really great points that are so wonderful to see written.

Community 158

Community Management Lean Software Review 158