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. Use some customer development to find out.

Lean 60

Lean San Francisco Continuous Deployment Cofounder 60

Startup Lessons Learned

FEBRUARY 22, 2009

That data is completely consonant with the people I know who are successful technologists today, and similar patterns are documented in each recent wave of technology innovation. I documented the lesson plans etc on [link] March 4, 2009 5:25 AM Eric said. Case Study: Continuous deployment makes releases n. Expo SF (May.

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

AUGUST 8, 2009

We owe a lot to this seminal document. The economics of these process trade-offs are discussed in the Principles of Product Development Flow.) Heres an excerpt: In a previous article, we called Toyota’s product development system the “second Toyota paradox.&# it is very helpful for me. Expo SF (May.

Software Review 87

Software Review Design Software San Francisco 87

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

FEBRUARY 7, 2013

Struggling to explain the successes and failures of those companies, I discussed principles like continuous deployment, customer development, and a hyper-accelerated form of agile. There's even a classic Wizard of Oz minimum viable product that dates back to 1998! The result: a new idea I called The Lean Startup.

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

OCTOBER 16, 2013

One good example is the way in which we''ve adjusted the length of different phases of our agile sprints. We don''t follow a set agile methodology, but rather follow a more home-grown, minimal version of various approaches. Continuous deployment: A key component of speed is to keep pushing out work.

Lean 167

Lean Startup Software Engineering Agile 167

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

MARCH 27, 2009

In fact, every single lean transformation documented in books like Lean Thinking took place in the midst of serious external threats. Customer Development : a disciplined approach to finding out if there is a market for your product before its too late. Case Study: Continuous deployment makes releases n.

San Francisco 117

San Francisco Lean Continuous Deployment DC 117

Startup Lessons Learned

NOVEMBER 13, 2008

Now, everyone is learning together - about your product, process, and team. 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.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

DECEMBER 6, 2008

When youve mastered that, consider adding operations, customer service, marketing, product management, business development - the idea is that when the team needs to get approval or support from another department, they already have an "insider" who can make it happen. Case Study: Continuous deployment makes releases n.

San Francisco 74

San Francisco SCRUM Lean Continuous Deployment 74

Startup Lessons Learned

APRIL 7, 2010

In fact, the curse of product development is that sometimes small things make a huge difference and sometimes huge things make no difference. When we’re optimizing, product development teams encounter similar situations. I mean, here we are, paying them to be there, and they won’t use the product!

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. Case Study: Continuous deployment makes releases n. If I am forced to make choices, I will stop using the bad choice, unless I am forced to use it. Interesting post.

PHP 166

PHP Software Review Ruby San Francisco 166

Startup Lessons Learned

SEPTEMBER 11, 2009

I offered an educated opinion about the travesty called "profit based pricing" that the former "community manager" actually fabricated documents as the basis to forum ban me and threatened to permanently ban me as a means to censor the information I sought to share. Case Study: Continuous deployment makes releases n.

Community 158

Community Management Lean Software Review 158