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. The new process let us manage the velocity of change in the codebase low, keeping the resistance manageable.

Lean 167

Lean Startup Software Engineering Agile 167

Startup Lessons Learned

FEBRUARY 20, 2009

Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. Similar results apply in product management, design, testing, and even operations. Normally I focus on the techniques you need to reduce batch size, like continuous integration.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

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. Let’s start with the startup personality attributes. for my more expansive definition).

San Francisco 161

San Francisco Management Founder Lean 161

Startup Lessons Learned

JULY 28, 2010

kaChing has been very active in the Lean Startup movement. If you havent seen it, Pascals recent presentation on continuous deployment is a must-see; slides are here. With case studies like this, we aim to illustrate specific Lean Startup techniques through the stories of current practitioners.

San Francisco 158

San Francisco Lean Continuous Deployment SEC 158

Startup Lessons Learned

AUGUST 3, 2009

Lessons Learned by Eric Ries Monday, August 3, 2009 Minimum Viable Product: a guide One of the most important lean startup techniques is called the minimum viable product. I was delighted to be asked to give a brief talk about the MVP at the inaugural meetup of the lean startup circle here in San Francisco.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

NOVEMBER 13, 2008

The five whys methodology has been around for some time, not just as a continuous improvement technique, but as a general problem solving method in all areas of management. As a management consultant who concentrates on thinking and problem solving, I use it often. The Lean Startup Intensive is tomorrow at Web 2.0.

Software Review 167

Software Review Technical Review San Francisco Continuous Deployment 167

Startup Lessons Learned

DECEMBER 16, 2009

Lessons Learned by Eric Ries Wednesday, December 16, 2009 What is Lean about the Lean Startup? That foundational idea, so clearly articulated in books like Lean Thinking, is what originally led me to start using the term lean startup. The following is a guest post for Startup Lessons Learned by the legendary Kent Beck.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

Startup Lessons Learned

MAY 7, 2009

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. Moreover, approaching the problem from the direction that I had intuitively is a recipe for never reaching a point where continuous deployment is feasible.

San Francisco 131

San Francisco Continuous Deployment Software Review Lean 131

Startup Lessons Learned

JANUARY 7, 2010

Lessons Learned by Eric Ries Thursday, January 7, 2010 Is Entrepreneurship a Management Science? My explicit goal in working with HBR is to foster a dialog between entrepreneurs and more traditional general managers. Is Entrepreneurship a Management Science? - Is Entrepreneurship a Management Science? Without further ado.

San Francisco 119

San Francisco Management Continuous Deployment Lean 119

Startup Lessons Learned

SEPTEMBER 10, 2008

I am convinced one of Joel Spolskys lasting contributions to the field of managing software teams will turn out to be the Joel Test , a checklist of 12 essential practices that you could use to rate the effectiveness of a software product development team. For more on continuous deployment, see Just-in-time Scalability.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

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. It was a great experience to see a relatively new startup hub in action - and thriving. Their model looks like a key ingredient in the startup brew there.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

OCTOBER 4, 2008

(Maybe youd like to start with The lean startup , How to listen to customers , or What does a startup CTO actually do? ) He serves on the advisory board of a number of technology startups, and has worked as a consultant to a number of startups, companies, and venture capital firms. So much for timing.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

JANUARY 12, 2010

Lessons Learned by Eric Ries Tuesday, January 12, 2010 Amazing lean startup resources A year ago, there was no lean startup movement. I continue to believe that the explosion of interest in the lean startup has very little to do with me. Rich also organized the first Lean Startup Meetup right here in San Francisco.

Lean 146

Lean San Francisco Wiki Startup 146

Startup Lessons Learned

JUNE 2, 2010

Lessons Learned by Eric Ries Wednesday, June 2, 2010 The Five Whys for Startups (for Harvard Business Review) I continue my series for Harvard Business Review with the Lean Startup technique called Five Whys. Techniques from lean manufacturing can be part of a startups innovation culture. Speed up or slow down?

Technical Review 132

Technical Review San Francisco Lean Continuous Deployment 132

Startup Lessons Learned

NOVEMBER 7, 2008

It was one of those brilliant startup brainstorms that comes to the team in a flash, with a giant thunderclap. Eric, Excellent article about an essential technique for startups. To help find the right keywords, Ive written an article on my blog Web Startup Help that details How to Do Keyword Research for startups.

Demand 167

Demand San Francisco Lean Continuous Deployment 167

Startup Lessons Learned

SEPTEMBER 7, 2008

The basic idea is to extend agile, which excels in situations where the problem is known but the solution is unknown, into areas of even greater uncertainty, such as your typical startup. Can this methodology be used for startups that are not exclusively about software? Talk about waste.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

NOVEMBER 14, 2013

Guest post by Lisa Regan, writer for T he Lean Startup Conference. We’ve posted the full program for The Lean Startup Conference , and it includes more than three days of events for Gold pass holders and six days of events for VIP pass holders. On the evening of December 8, Ignite Lean Startup kicks off the conference.

Continuous Deployment 162

Continuous Deployment Norway Lean Analytics 162

Startup Lessons Learned

SEPTEMBER 15, 2008

Lessons Learned by Eric Ries Monday, September 15, 2008 The one line split-test, or how to A/B all the time Split-testing is a core lean startup discipline, and its one of those rare topics that comes up just as often in a technical context as in a business-oriented one when Im talking to startups. First of all, why split-test?

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

NOVEMBER 8, 2008

This theory has become so influential that I have called it one of the three pillars of the lean startup - every bit as important as the changes in technology or the advent of agile development. I highly recommend this book for all entrepreneurs, in startups as well as in big companies. Very few startups fail for lack of technology.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

NOVEMBER 4, 2008

Lessons Learned by Eric Ries Tuesday, November 4, 2008 Principles of Lean Startups, presentation for Maples Investments Image via Wikipedia Steve Blank and I had the opportunity to create a presentation about lean startups for Maples Investments. My path to lean startups began with Kent Beck and extreme programming.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

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. My intention is to describe a full working process, similar to what I’ve seen at IMVU and other lean startups. First, a caveat.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

JANUARY 4, 2009

Lessons Learned by Eric Ries Sunday, January 4, 2009 Sharding for startups The most important aspect of a scalable web architecture is data partitioning. Sharding for startups To support a single partitioning scheme is easy, especially if you design for it from the start. But startups rarely have either luxury. to store it.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

JULY 29, 2009

Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage. In a startup, we should take full advantage of our options, even if they feel dirty or riddled with technical debt. Startups are always moving, so invest in moving faster and better.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

FEBRUARY 22, 2010

For startups (and other innovators ), that’s a decisive advantage. The work itself, especially in startups, depends primarily on intelligence, communication, creativity and empathy. Vivek Wadhwa and his team continue their excellent work investigating the true nature of entrepreneurship.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

Startup Lessons Learned

JULY 6, 2009

Lessons Learned by Eric Ries Monday, July 6, 2009 Lean Startup fbFund slides and video As a follow-up to my previous post on my talk for fbFund at Facebook , there was enough interest in watching video of the talk that I have finally uploaded it using Apples MobileMe. If you want to see the original video, use the link above.

Lean 115

Lean Video San Francisco Continuous Deployment 115

Startup Lessons Learned

APRIL 4, 2010

Lessons Learned by Eric Ries Sunday, April 4, 2010 Kent Beck keynote, "To Agility, and Beyond" Kent Beck will give the opening keynote at the Startup Lessons Learned conference on April 23. His keynote will kick off the day as well as our module on the build phase of the fundamental feedback loop that powers all startups. Expo SF (May.

Agile 99

Agile Software Review San Francisco Continuous Deployment 99

Startup Lessons Learned

MARCH 16, 2009

Jim Murphy is a long-time agile practitioner in startups. But startups sometimes have trouble applying agile successfully. Embedded in that assumption is why startups fail. Notice that the unit of progress changes as we move from waterfall to agile to the lean startup. Hes often felt that there was something missing.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

JUNE 17, 2010

Startups are companies. Startups aspire to become big companies. Therefore, startups should have departments. Each of these benefits also exists in startups, which is why most startups are also organized in departments. I once worked at a startup with an exceptional functional department system.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

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. Without entering into that theoretical domain, in this post Id like to try and offer a specific and concrete suggestion for how to build a culture of learning into a startup.

Employee 146

Employee San Francisco Lean Software Review 146

Startup Lessons Learned

MARCH 22, 2010

Lessons Learned by Eric Ries Monday, March 22, 2010 The new startup arms race (for Huffington Post) The Huffington Post published an op-ed on the Startup Visa movement that Ive been working on for some time. The New Startup Arms Race Americas future prosperity depends on our ability to maintain this lead.

San Francisco 121

San Francisco Indiana Lean Startup 121

Startup Lessons Learned

MARCH 25, 2010

(for Harvard Business Review) Over at Harvard Business Review, Ive been building up a series designed to introduce the Lean Startup methodology to a business-focused audience. Read the rest of The Startups Rules of Speed - The Conversation - Harvard Business Review. 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

SEPTEMBER 2, 2008

Labels: agile , continuous deployment 1 comments: timothyfitz said. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R. The Lean Startup Intensive is tomorrow at Web 2.0. Expo SF (May. . Expo SF (May.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

FEBRUARY 22, 2009

:-) January 15, 2010 1:29 AM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Expo SF (May. .

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

SEPTEMBER 13, 2008

Its now a technique I recommend for any web-based startup. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? No departments The Five Whys for Startups (for Harvard Business R. The Lean Startup Intensive is tomorrow at Web 2.0. Startup Lessons Learned - the Conference (April 23.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

DECEMBER 8, 2008

My manager, part of the QA group, gave me a tour of a site and we entered a huge depressing warehouse stacked full with cubes. As with many lean startup practices, its getting started thats the hard part. Still, my experience working with startups has been that too much time spent talking about advanced topics can lead to inaction.

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136

Startup Lessons Learned

JUNE 5, 2009

Lessons Learned by Eric Ries Friday, June 5, 2009 It’s a startup, not a spreadsheet Some people, when they start to realize the power of using data to inform their decisions, become obsessed with optimization. Unfortunately, most decisions that confront startups lack a definitive right answer. But this is wrong, too.

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102

Startup Lessons Learned

SEPTEMBER 2, 2008

October 17, 2009 10:34 AM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Subscribe via email Blog Archive ► 2010 (48) ► October (3) Case Study: Rapid iteration with hardware The Lean Startup Bundle Stop lying on stage ► September (4) Good enough never is (or is it?) Expo SF (May. .

San Francisco 142

San Francisco Continuous Deployment Lean DC 142