Startup Lessons Learned

SEPTEMBER 7, 2008

Lessons Learned by Eric Ries Sunday, September 7, 2008 Customer Development Engineering Yesterday, I had the opportunity to guest lecture again in Steve Blank s entrepreneurship class at the Berkeley-Columbia executive MBA program. Can this methodology be used for startups that are not exclusively about software?

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

FEBRUARY 20, 2009

Lessons Learned by Eric Ries Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. I owe it originally to lean manufacturing books like Lean Thinking and Toyota Production System. For software, the easiest batch to see is code. This is easiest to see in deployment.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

SEPTEMBER 2, 2008

We wanted an agile approach that would allow us to build our software architecture as we needed it, without downtime, but also without large amounts of up-front cost. After all, the worst kind of waste in software development is code to support a use case that never materializes. April 23, 2010 in San Francisco.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

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. They just assumed it was the way software companies worked. Sound good?

Software Review 164

Software Review Engineer Management Technical Review 164

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. Please leave feedback!) Do you fix bugs before writing code?

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

MARCH 16, 2009

In most agile development systems, there is a notion of the "product backlog" a prioritized list of what software is most valuable to be developed next. The breakthrough idea of agile is that software should be built iteratively, with the pieces that customers value most created first.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

JULY 30, 2009

I thought Id share a little bit of that, too: I’ve been interested in different approaches to software development going back to 1987 when – in my first company Feld Technologies – my partner Dave Jilk and I started talking about “semi-custom software development&# (way ahead of its time).

Lean 68

Lean San Francisco Continuous Deployment DC 68

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. Were a software company, so what we do everyday is turn ideas into code.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

NOVEMBER 6, 2008

Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective. But its helpful to take a detailed look inside the highly agile process used by Google to ship software. Lean Startup Wiki - including a complete list of local meetups and meetup organizers.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

Startup Lessons Learned

SEPTEMBER 2, 2008

Lessons Learned by Eric Ries Tuesday, September 2, 2008 On deployment My favorite question to ask a software development team is "how do you do a release." How long does the software sit un-deployed? Software is generally always getting better or getting worse. How fast do they iterate? Does it require weeks of QA?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

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. One is used by engineers to refer to the process of getting code fully integrated into production.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

OCTOBER 4, 2008

Although Catalyst folded with the dot-com crash, Ries continued his entrepreneurial career as a Senior Software Engineer at There.com, leading efforts in agile software development and user-generated content. I know many people who think that software works like magic, but to me it actually was magic.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

SEPTEMBER 30, 2008

It became harder and harder to separate how the software is built from how the software is structured. If not, whos going to insist we switch to free and open source software? Labels: product development 15comments: mukund said. Thoughts on scientific product development Lo, my 5 subscribers, who are you?

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

NOVEMBER 4, 2008

It is becoming easier and cheaper for companies to bring products to market, leveraging free and open source software , cloud computing, open social data (Facebook, OpenSocial ), and open distribution (AdWords, SEO). Agile software development. Agile allows companies to build higher quality software faster.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

bizthoughts.mikelee.org

MARCH 8, 2012

Active software engineers probably get two offers a month or more. I was able to hire phenomenal software engineers and grow a strong team culture. If you’re a non-technical entrepreneur in Silicon Valley that’s out of college now, it can be tough to find a technical cofounder. I was lucky enough to have worked for Yahoo!

Technical Cofounder 40

Technical Cofounder Cofounder Technical Review Software Review 40

Startup Lessons Learned

FEBRUARY 9, 2009

It uses principles of agile software development, open source and web 2.0, Hey Someone else who is extending the agile/lean approach beyond just developing software. a guide for hackers) You buy virtual goods The free software hiring advantage Continuous deployment and continuous learning The lean startup @ Web 2.0

Lean 68

Lean San Francisco Web Advisory Board 68

Startup Lessons Learned

SEPTEMBER 1, 2008

Lessons Learned by Eric Ries Monday, September 1, 2008 Test-Driven Development as andon cord You cannot control what you cannot see, and the hardest part of managing software projects is that the final product is so intangible. Thoughts on scientific product development Lo, my 5 subscribers, who are you?

San Francisco 68

San Francisco Developer Continuous Deployment DC 68

Startup Lessons Learned

OCTOBER 5, 2008

So the product manager winds up actually having to use the software, by hand, updating the spec and helping create a new test plan. But first I think we need to save the product manager from that special form of torture only a waterfall product development team can create. This post has been removed by the author.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

APRIL 14, 2009

Their product definition fluctuates wildly – one month, it’s a dessert topping, the next it’s a floor wax. Their product development team is hard at work on a next-generation product platform, which is designed to offer a new suite of products – but this effort is months behind schedule.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

DECEMBER 28, 2009

Or, phrased more hopefully, "I see how you can use continuous deployment to run an online consumer service, but how can it be used for B2B software?" That continuous deployment leads to lower quality software than software built in large batches. Or variations thereof. Implicit in these concerns are two beliefs: 1.

Continuous Deployment 122

Continuous Deployment San Francisco Lean Metrics 122

Startup Lessons Learned

JANUARY 2, 2009

My son is planning a software product that will take the mystery out of wikis and make the technology easier for consumers to use. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Funnel averages over time. You can read the article to find out why. 3comments: Charles Crawford said.

San Francisco 60

San Francisco Tampa Continuous Deployment Lean 60

Startup Lessons Learned

MARCH 25, 2009

Agile Vancouver : Lean Development for Lean Times On Tuesday April 21st, we are hosting an afternoon event on the application of Lean Principles to software development. This workshop brings together leading thinkers from Lean Production and Lean software. April 23, 2010 in San Francisco. Bring your questions.

Agile 60

Agile Lean San Francisco Continuous Deployment 60

Startup Lessons Learned

NOVEMBER 8, 2008

Lessons Learned by Eric Ries Saturday, November 8, 2008 What is customer development? When we build products, we use a methodology. For software, we have many - you can enjoy a nice long list on Wikipedia. Customer development is a parallel process to product development, which means that you dont have to give up on your dream.

Customer Development 168

Customer Development Developer San Francisco Customer 168

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. The biggest source of waste in new product development is building something that nobody wants. Leverage product development with open source and third parties.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

MAY 31, 2010

Kent Beck is deservedly famous for his many contributions in the software industry. Kent Beck is deservedly famous for his many contributions in the software industry. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Do you know the difference between Durant and Sloan ? Bring your questions.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

Startup Lessons Learned

JULY 5, 2010

While the customer development framework of Four Steps is universally relevant, The Entrepreneur’s Guide updates its practices for modern startups. Four Steps primarily centers its stories and case studies on B2B hardware and software startups. Lean Startup Wiki - including a complete list of local meetups and meetup organizers.

Customer Development 166

Customer Development Developer San Francisco Customer 166

Startup Lessons Learned

SEPTEMBER 8, 2008

It felt like software that grownups were supposed to use, and we didnt qualify. It cost us a few hundred thousand dollars to get our app up and running, but none of that was dollars spent on software licenses or professional services. Thoughts on scientific product development Lo, my 5 subscribers, who are you?

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

Startup Lessons Learned

SEPTEMBER 10, 2008

His post is ostensibly about how often to release new work (whether youre a blog writer, movie star, software team.) I’ve been in the software industry for a long time. Thoughts on scientific product development Lo, my 5 subscribers, who are you? That’s all fine and dandy. Is that mass all that critical?

San Francisco 76

San Francisco Continuous Deployment Lean DC 76

Startup Lessons Learned

AUGUST 26, 2009

More recently it's skewed to software & web. Revisiting the Software Design Manifesto (and what. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. I remember thinking then how much better it was than Chicago, where I'd spent the previous 8 years. April 23, 2010 in San Francisco.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

Startup Lessons Learned

MAY 27, 2009

It uses principles of agile software development, open source and web 2.0, Ship new software at a dizzying pace: multiple times a day while improving quality and lowering costs. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. April 23, 2010 in San Francisco. Bring your questions.

Lean 60

Lean Austin San Francisco Continuous Deployment 60

Startup Lessons Learned

SEPTEMBER 22, 2008

Lessons Learned by Eric Ries Monday, September 22, 2008 Thoughts on scientific product development I enjoyed reading a post today from Laserlike (Mike Speiser), on Scientific product development. I agree with the less is more product development approach, but for a different reason. Now that is fun.

Product Development 68

Product Development Developer San Francisco Product 68

Startup Lessons Learned

MARCH 17, 2009

Although Im not a developer, I am captivated by the lean and agile start-up model that you write about. I plan to apply these models to my own ventures, especially within new contexts separate from software and web development. Lean Startup Wiki - including a complete list of local meetups and meetup organizers.

Lean 76

Lean San Francisco Web Continuous Deployment 76

Startup Lessons Learned

APRIL 18, 2010

Lean, when used in the context of lean startup, refers to a process of building companies and products using lean manufacturing principles applied to innovation. That process involves rapid hypothesis testing, validated learning about customers , and a disciplined approach to product development. April 23, 2010 in San Francisco.

Lean 167

Lean San Francisco Continuous Deployment Startup 167

Startup Lessons Learned

FEBRUARY 11, 2009

Lessons Learned by Eric Ries Wednesday, February 11, 2009 The free software hiring advantage This is one of those startup tips Im a little reluctant to share, because its been such a powerful source of competitive advantage in the companies Ive worked with. Especially for a startup, not taking maximum advantage of free software is crazy.

Software Review 68

Software Review Software Hiring San Francisco 68

Startup Lessons Learned

MAY 14, 2009

This shift allowed us to crank out working software quickly as a service. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. We attempted to use Waterfall and market ourselves as B2C. It was a disaster. We changed our model to B2B and adopted Agile around 2002. April 23, 2010 in San Francisco.

Lean 60

Lean San Francisco Continuous Deployment Software Review 60

Startup Lessons Learned

FEBRUARY 22, 2009

MUDs made the essential truth about software into a powerful metaphor: that code is magic, giving those who wield it the ability to create new forms of value literally out of thin air. a guide for hackers) You buy virtual goods The free software hiring advantage Continuous deployment and continuous learning The lean startup @ Web 2.0

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

SEPTEMBER 18, 2008

Its enourmously helpful when you need to generate new ideas about what to do, or when you face a product problem you dont know how to solve. For example, we used to be baffled at IMVU by the significant minority of people who would download the software but never chat with anyone. April 23, 2010 in San Francisco. Bring your questions.

San Francisco 133

San Francisco Lean Continuous Deployment DC 133