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

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). Read the rest.

Lean 68

Lean San Francisco Continuous Deployment DC 68

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. hey eric, love the blog.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

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

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. For software, the easiest batch to see is code. When something goes wrong with production software, its almost always because of an unintended side-effect of some piece of code.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

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

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. All customers will see the new software as soon as it’s deployed.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

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. You can tell a lot about a company from their deployment flow.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

FEBRUARY 28, 2009

This builds on a lot of great thinking that has come before, like the agile movements insistence that only the creation of working code counts as progress for a software development team. a guide for hackers) You buy virtual goods The free software hiring advantage Continuous deployment and continuous learning The lean startup @ Web 2.0

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

FEBRUARY 10, 2009

That leads to a seemingly-obvious question: what is progress in software development? Did it ever occur to any of you how many man hours are wasted on writing software that gets thrown out because you didnt simply ask the user if they would even like that feature? Heck, thats what it says right there in the agile manifesto.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

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. Were a software company, so what we do everyday is turn ideas into code. Lean Startup Wiki - including a complete list of local meetups and meetup organizers.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

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. Bring your questions.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

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

DECEMBER 16, 2009

For those whove heard it, it contains a length discourse on the subject of agile software development and extreme programming, including its weaknesses when applied to startups. I had a background in lean manufacturing (book knowledge, anyway) and lean software development (hands on) before encountering Lean Startups.

Lean 140

Lean San Francisco Continuous Deployment Startup 140

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. Please register to attend this event as space will be limited.

Agile 60

Agile Lean San Francisco Continuous Deployment 60

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. In almost all Agile Development systems, thousands of automated tests are run against every change to the software.

San Francisco 68

San Francisco Developer Continuous Deployment DC 68

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. Hes often felt that there was something missing.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

DECEMBER 8, 2008

In many traditional software organizations, branches can be extremely long-lived, and integrations can take weeks or months. Heres how Fowler describes it: I vividly remember one of my first sightings of a large software project. I would like the users of my software to test and give their feedback to me. Rate me on some scale.

Software Review 136

Software Review San Francisco Lean Continuous Deployment 136

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

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!) They just dont happen. April 23, 2010 in San Francisco.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

JULY 5, 2010

Four Steps primarily centers its stories and case studies on B2B hardware and software 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. April 23, 2010 in San Francisco.

Customer Development 166

Customer Development Developer San Francisco Customer 166

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 Continuous Deployment 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 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? Lean Startup Wiki - including a complete list of local meetups and meetup organizers. But along the way, something strange happened.

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

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. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. The fourth spec exists only in these emails, which are changing the design in an ad-hoc fashion. Bring your questions.

San Francisco 158

San Francisco Management Software Review Product 158

Startup Lessons Learned

OCTOBER 20, 2008

They just assumed it was the way software companies worked. Unfortunately, threats work a lot better at incentivizing people to CYA than getting them to write quality software. When I first encountered agile software techniques, in the form of extreme programming , I thought I had found the answer. Sound good? It didnt work.

Software Review 164

Software Review Engineer Management Technical Review 164

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. Lean Startup Wiki - including a complete list of local meetups and meetup organizers.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

Startup Lessons Learned

SEPTEMBER 22, 2008

Heres something I can relate to: We used assembla for subversion, scrums, milestones, wikis, and for general organizational purposes. My favorite instance of this is scheduling software. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. April 23, 2010 in San Francisco. Bring your questions.

San Francisco 68

San Francisco SCRUM Lean Continuous Deployment 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. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. 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 1, 2009

We might be a ways away from the reality of a Chief Engineer or Product Director role commonly in software development, but ultimately it's going to be a matter of getting the culture right so that people stick around long enough to develop not only the tactical skills, but also the honed instincts and senses. Bring your questions.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

MARCH 17, 2009

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. Although Im not a developer, I am captivated by the lean and agile start-up model that you write about. Bring your questions.

Lean 76

Lean San Francisco Web Continuous Deployment 76

Startup Lessons Learned

JULY 2, 2009

We started with a simple wiki page with a few bullet points of things that new engineers had tripped over recently. Furthermore, I think most of what you are suggesting is applicable in companies/ industries that are not software development. It's so old and so buggy that it's a real pain to ship 3D software on it.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

MARCH 27, 2009

I believe it is a full, company-wide turn through the OODA loop (for a software business, see especially Ideas-Code-Learn ). I am thinking of the Toyota system and adjusting the "big cogs" in the wheel and its relevance to enterprise software and services (i.e. What counts as an iteration? March 31, 2009 7:51 PM Paul Sweeney said.

San Francisco 117

San Francisco Lean Continuous Deployment DC 117

Startup Lessons Learned

APRIL 26, 2009

We combined three tactics: extensive use of free software, an open platform for user-generated content, and leveraged distribution channels. In that same spirit, here are some suggestions for tactics you can use to increase the leverage of your product development efforts: Free and open source software (and even hardware ).

Product Development 88

Product Development Developer San Francisco Product 88

Startup Lessons Learned

NOVEMBER 8, 2008

For software, we have many - you can enjoy a nice long list on Wikipedia. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Lessons Learned by Eric Ries Saturday, November 8, 2008 What is customer development? When we build products, we use a methodology. April 23, 2010 in San Francisco.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

JANUARY 28, 2009

Its an essential discipline of good software development, especially in startups. Often, a simple mailing list or wiki is good enough, but judge based on the results. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Heres a company I met with recently. Practice five whys.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

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