Startup Lessons Learned

FEBRUARY 9, 2009

Lessons Learned by Eric Ries Monday, February 9, 2009 The lean startup @ Web 2.0 Expo (and a call for help) Ive been asked to speak this year at the Web 2.0 The Lean Startup: a Disciplined Approach to Imagining, Designing, and Building New Products.: It uses principles of agile software development, open source and web 2.0,

Lean 68

Lean San Francisco Web Advisory Board 68

Startup Lessons Learned

AUGUST 8, 2009

Lessons Learned by Eric Ries Saturday, August 8, 2009 Revisiting the Software Design Manifesto (and whats changed since then) My recent article on technical debt and its positive uses generated a fair bit of controversy. The same might be said of good software. Here we have the beginnings of a theory of design for software.

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

MARCH 17, 2009

Lessons Learned by Eric Ries Tuesday, March 17, 2009 Join the Lean Startup discussion at Web 2.0 Expo for free Im honored to announce that my Lean Startup session at the Web 2.0 Although Im not a developer, I am captivated by the lean and agile start-up model that you write about. The chance to not only be at the Web 2.0

Lean 76

Lean San Francisco Web Continuous Deployment 76

Startup Lessons Learned

SEPTEMBER 15, 2008

But by taking advantage of open source, agile software, and iterative development, lean startups can operate with much less waste. I am heavily indebted to earlier theorists, and highly recommend the books Lean Thinking and Lean Software Development. The Lean Startup Intensive is tomorrow at Web 2.0.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Startup Lessons Learned

SEPTEMBER 7, 2008

In addition to presenting the IMVU case, we tried for the first time to do an overview of a software engineering methodology that integrates practices from agile software development with Steves method of Customer Development. Can this methodology be used for startups that are not exclusively about software?

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Hearpreneur

SEPTEMBER 22, 2021

Tesla has always put a huge emphasis on product development and technological advancement. This software enables us to communicate with coworkers and connect with family members that we hope to see safely again soon. Lastly, Microsoft Office remains the most popular corporate productivity software program.

Technical Review 124

Technical Review Entrepreneur Software Review SEO 124

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. Expo SF (May. for Harvard Business Revie.

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

crowdSPRING Blog

MAY 11, 2012

These posts and videos are about logo design , web design , startups, entrepreneurship, small business, leadership, social media, marketing, and more! Web Tool of the Month: crowdSPRING – [link]. Better Agile Than Smart – [link]. Six Myths of Product Development – [link]. – [link].

Social Media 92

Social Media Small Business Design Media 92

Steve Blank

JANUARY 6, 2014

For the last 75 years products (both durable goods and software) were built via Waterfall development. This process forced companies to release and launch products by model years, and market new and “improved” versions. The Old Days – Waterfall Product Development. Waterfall – The Customer View.

Continuous Deployment 330

Continuous Deployment Customer Agile Cloud 330

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. This is still an essential practice, especially on the web.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

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

NOVEMBER 4, 2008

Boyd emphasized the importance of agility in combat: "the key to victory is to be able to create situations wherein one can make appropriate decisions more quickly than ones opponent." Agile software development. Agile allows companies to build higher quality software faster. Expo SF (May.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

MAY 31, 2010

Lessons Learned by Eric Ries Monday, May 31, 2010 Thank you The past month has been an incredible roller coaster: #sllconf was a trending topic (briefly topping Justin Bieber before the wifi in the hotel gave out), the Web 2.0 Kent Beck is deservedly famous for his many contributions in the software industry.

San Francisco 133

San Francisco Lean Technical Review Software Review 133

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

JULY 29, 2009

I hope to show why lean and agile techniques actually reduce the negative impacts of technical debt and increase our ability to take advantage of its positive effects. Startups especially can benefit by using technical debt to experiment, invest in process, and increase their product development leverage.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

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. Expo SF (May.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

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. Eventually, I hope to get them on a full agile diet, with TDD, scrums, sprints, pair programming, and more. Labels: product development 8comments: Vincent van Wylick said.

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

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

SEPTEMBER 30, 2008

It became harder and harder to separate how the software is built from how the software is structured. If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? If not, whos going to insist we switch to free and open source software? I dont think so.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

JANUARY 18, 2010

Lessons Learned by Eric Ries Monday, January 18, 2010 Case Study: Continuous deployment makes releases non-events The following is a case study of one entrepreneurs transition from a traditional development cycle to continuous deployment. Many people still find this idea challenging, even for companies that operate solely on the web.

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

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. You can learn about customer development, and quite a bit more, in Steves book The Four Steps to the Epiphany.

Customer Development 168

Customer Development Developer San Francisco Customer 168

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

Venture Chronicles

JUNE 29, 2010

I was on vacation last week with my family and did not post anything but I have been wanting to write about a meeting I had with Accept Software a few weeks ago so I went through my notes and refreshed myself on the conversation, which was interesting in many dimensions. Tags: Uncategorized accept software.

Software 34

Software Portfolio Agile Retention 34

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. The Lean Startup Intensive is tomorrow at Web 2.0. Automated tests make defects visible.

San Francisco 68

San Francisco Developer Continuous Deployment DC 68

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

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

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

AUGUST 26, 2009

Thank you @ericries for drastically altering my perception of agile startup Thank you all so much for your kind words. More recently it's skewed to software & web. The Lean Startup Intensive is tomorrow at Web 2.0. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Expo SF (May.

San Francisco 113

San Francisco Silicon Valley Startup Lean 113

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

Customer Development 166

Customer Development Developer San Francisco Customer 166

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. The Lean Startup Intensive is tomorrow at Web 2.0. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0,

Lean 60

Lean Austin San Francisco Continuous Deployment 60

Up and Running

MAY 23, 2016

Since the term “cloud computing” was coined in 1996—at least as we have come to understand its meaning—the software as a service industry has exploded. If you use software like LivePlan, you can create this initial “lean plan” in under an hour and then spend your time where it really matters—on validating your idea.

Software Review 74

Software Review Software Delaware Forecast 74

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. The Lean Startup Intensive is tomorrow at Web 2.0. I dont really remember why it didnt work.

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. The Lean Startup Intensive is tomorrow at Web 2.0. Tell your Startup Visa story Speaking 2010: Webstock, GDC, Web 2.0, Expo SF (May.

San Francisco 76

San Francisco Continuous Deployment Lean DC 76

Startup Lessons Learned

MAY 14, 2009

Were not going to have any form of advertising, but I am considering trying to offer a scholarship program to worthy entrepreneurs, just as we did for the Web 2.0 We changed our model to B2B and adopted Agile around 2002. This shift allowed us to crank out working software quickly as a service. Expo SF (May.

Lean 60

Lean San Francisco Continuous Deployment Software Review 60

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. My startup business (web development) is being shunned by virtually every other potential investor I approached thus far. The Lean Startup Intensive is tomorrow at Web 2.0.

San Francisco 60

San Francisco Tampa Continuous Deployment Lean 60

Startup Lessons Learned

AUGUST 24, 2009

When I reviewed a recent product development book, it immediately shot up to Amazon sales rank 300. As you and I have chatted about, a Zynga developed game versus an EA developed game is quite different. Though technology tools and Web 2.0 The Lean Startup Intensive is tomorrow at Web 2.0. Is that a lot?

San Francisco 113

San Francisco Lean Technical Review Distribution 113