Startup Lessons Learned

JULY 3, 2009

Lessons Learned by Eric Ries Friday, July 3, 2009 Lean Startup fbFund wrap-up Last week I had a real blast meeting with the companies at the fbFund incubator at Palo Alto. The Lean Startup fbFund Edition View more documents from Eric Ries. Use some customer development to find out. Without further ado. Expo SF (May.

Lean 60

Lean San Francisco Continuous Deployment Cofounder 60

Startup Lessons Learned

OCTOBER 20, 2008

Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their product development process. Even worse, agile wasnt really helping me ship higher quality software.

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

FEBRUARY 7, 2013

Last May, I shared the news that long-time Lean Startup advocates Brant Cooper and Patrick Vlaskovits were working on a new book called The Lean Entrepreneur featuring illustrations by FAKEGRIMLOCK. LitMotors approach to using Lean Startup to create a new vehicle category. That new book is about to hit bookstores everywhere.

Lean 167

Lean Entrepreneur Agile San Francisco 167

Startup Lessons Learned

MAY 31, 2010

Expo Intensive rocked, the mainstream media has started writing about the Lean Startup, and - most of all - the movement continues to grow and evolve. I went to the conference thinking that I was well grounded in the basics of the Lean Startup approach and that attendance would hone the edges of that understanding.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

JUNE 15, 2009

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. It lets the customer and development team spot problems with calculations almost immediately.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

SEPTEMBER 2, 2008

Its inspired by the classic OODA Loop and is really just a simplified version of that concept, applied specifically to creating a software product development team. There are three stages: We start with ideas about what our product could be. How about documentation that nobody reads? the data on a regular basis.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Both Sides of the Table

NOVEMBER 1, 2009

I know that this all seems obvious now with the movements started by Steven Blank ( Four Steps of Epiphany ) with the whole Customer Development processes / Lean Startup movements also popularized by people like Eric Ries. They had decided to take a Digg style approach to product development. Back then it seemed foreign.

Customer 280

Customer Technical Review Software Review Mexico 280

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. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Steve Blank

JANUARY 6, 2014

This process forced companies to release and launch products by model years, and market new and “improved” versions. In the last few years Agile and “Continuous Deployment” has replaced Waterfall and transformed how companies big and small build products. The Old Days – Waterfall Product Development.

Continuous Deployment 332

Continuous Deployment Customer Agile Cloud 332

Startup Lessons Learned

AUGUST 8, 2009

We owe a lot to this seminal document. Lean methods present a third option: to invest in our process so that our design gets more feedback sooner and is more adaptable to changes in purpose. The economics of these process trade-offs are discussed in the Principles of Product Development Flow.) it is very helpful for me.

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

OCTOBER 16, 2013

Guest post by Lisa Regan, writer for The Lean Startup Conference. As Lean Startup methods have been used now for a number of years, we’ve become increasingly interested in how companies use them to sustain growth. One good example is the way in which we''ve adjusted the length of different phases of our agile sprints.

Lean 167

Lean Startup Software Engineering Agile 167

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. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May.

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Steve Blank

SEPTEMBER 3, 2009

This post describes how the traditional product development model distorts startup sales, marketing and business development. The Use of a Product Development Model to Measure Sales Using the product development diagram for startup sales activities is like using a clock to tell the temperature.

Customer Development 229

Customer Development Developer Silicon Valley Customer 229

Steve Blank

SEPTEMBER 17, 2009

This post describes a solution – the Customer Development Model. In future posts I’ll describe how Eric Ries and the Lean Startup concept provide the equivalent model for product development activities inside the building and neatly integrates customer and agile development.

Customer Development 256

Customer Development Developer Customer Silicon Valley 256

Startup Lessons Learned

AUGUST 16, 2010

First, SlideShare is a fantastic product (that I use on a regular basis) and an impressive company example of Lean Startup practices in action. Second, their story illustrates a key Lean Startup idea: proving the business in micro-scale. As this is a new initiative for this blog, we especially welcome your feedback.

San Francisco 167

San Francisco Lean Analytics Continuous Deployment 167

Startup Lessons Learned

NOVEMBER 5, 2008

Education Guideline Book (1st Edition) Sep 2006 View SlideShare document or Upload your own. The Lean Startup Intensive is tomorrow at Web 2.0. Startup Visa update ► February (5) Kiwi lean startup + Australia next Why diversity matters (the meritocracy business) Beware of Vanity Metrics (for Harvard Business Rev.

Advertising 60

Advertising San Francisco Media Continuous Deployment 60

Up and Running

MAY 23, 2016

Step 1: Start with a lean plan. It’s the fastest way to get your idea onto paper, and it’s the very first step in the lean planning process, which is much easier and more iterative than traditional business planning methods. In this section, you really just want to document how your business will make money. Schedule.

Software Review 74

Software Review Software Delaware Forecast 74

Startup Lessons Learned

MARCH 27, 2009

In lean times, it’s most important to focus on cutting costs in ways that speed you up, not slow you down. In fact, every single lean transformation documented in books like Lean Thinking took place in the midst of serious external threats. And, of course, theres the Lean Startup session at the upcoming Web 2.0

San Francisco 117

San Francisco Lean Continuous Deployment DC 117

Steve Blank

NOVEMBER 4, 2021

Lean Methodology consists of three tools designed for entrepreneurs building new ventures: The Business Model Canvas – to write down all the hypotheses about a new business; Customer Development – a process for testing those hypotheses outside the building; Agile Engineering – to rapidly build minimal viable products to test product/market fit.

Customer 427

Customer Marketing Lean Vertical 427

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. Wed never heard of five whys, and we had plenty of "agile skeptics" on the team. Great related post by John Shook at the Lean Enterprise Institute about technical vs. social sides of problems.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

APRIL 7, 2010

Lessons Learned by Eric Ries Wednesday, April 7, 2010 Learning is better than optimization (the local maximum problem) Lean startups don’t optimize. In fact, the curse of product development is that sometimes small things make a huge difference and sometimes huge things make no difference. That’s the local maximum.

San Francisco 154

San Francisco Lean Metrics Design 154

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. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 74

San Francisco SCRUM Lean Continuous Deployment 74

A Smart Bear: Startups and Marketing for Geeks

FEBRUARY 7, 2011

With all these new tasks, there’s no way you can also manage the projects and client relationships and internal product development, so you’ll need a project manager or a sales person or an office manager or some kind of help, and all of those come out of your profits. None of these new tasks are fun or creative.

America 330

America Employee Hiring HTML 330

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. The Lean Startup Intensive is tomorrow at Web 2.0. If I am forced to make choices, I will stop using the bad choice, unless I am forced to use it. will make the foundation weak.

PHP 166

PHP Software Review Ruby San Francisco 166

steveblank.com

JULY 8, 2011

Github - Free public repositories, collaborator management, issue tracking, wikis, downloads, code review, graphs Pivotal Tracker – Agile project management tool that enables real time collaboration. WebSequenceDiagrams - sketch sequence diagrams. Lighthouse – Issue Tracking Tool.

Software Review 110

Software Review Startup Silicon Valley Analytics 110

www.vccafe.com

MARCH 11, 2013

For modifications, please edit the original document here. Lean Methodology Sources. Steve Blank on Lean Customer Development. Part 3- Lean Cust. Scanning / Document Management. Steve Blank’s Lean Startup Resources. Lean Startup Circle â?? Agile project management. Codeacademy.

Software Review 53

Software Review Technical Review Startup 53

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. The Lean Startup Intensive is tomorrow at Web 2.0.

Community 158

Community Management Lean Software Review 158