Startup Lessons Learned

SEPTEMBER 7, 2008

We talk about taking advantages of the incredible agility offered by modern web architecture for extremely rapid deployment, etc. One major theory that has influenced the way I think about processes comes from Lean Manufacturing , where they use these same techniques to build cars. Expo SF (May. for Harvard Business Revie.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

Startup Lessons Learned

JUNE 17, 2010

They are leaders, visionaries, founders and managers having tremendous success. I suggested that we change the underlying architecture of our UI system so that the artists would be able to build their own UI pieces themselves and then integrate them into the product without requiring new code every time.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

AUGUST 8, 2009

And as Kapor himself points out, the core ideas have even older origins: The Roman architecture critic Vitruvius advanced the notion that well-designed buildings were those which exhibited firmness, commodity, and delight. This includes the designers as well as the engineers and product managers. We owe a lot to this seminal document.

Software Review 87

Software Review Design Software San Francisco 87

www.subelsky.com

FEBRUARY 25, 2010

Mike Subelskys Blog Wednesday, November 11, 2009 Lean startup tools for Rails apps A few months ago I was invited to dinner with the Geeks on a Plane crew when they stopped in Washington, and had the opportunity to meet one of my heroes, Eric Ries , author of the Startup Lessons Learned blog. Email This BlogThis!

Lean 41

Lean Baltimore Ruby Maryland 41

Startup Lessons Learned

FEBRUARY 16, 2009

Lessons Learned by Eric Ries Monday, February 16, 2009 Continuous deployment with downloads One of my goals in writing posts about topics like continuous deployment is the hope that people will take those ideas and apply them to new situations - and then share what they learn with the rest of us. Thanks for the comments.

Continuous Deployment 68

Continuous Deployment San Francisco Software Review Lean 68

Startup Lessons Learned

SEPTEMBER 8, 2008

So did I when I finally found myself building an app with real scalability, a few years later, but a combination of our just-in-time scalability technique and great open source scaling tools, made it manageable. You dont need to invent a new architecture, and you dont need to even build your architecture up-front. Expo SF (May.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

Startup Lessons Learned

APRIL 26, 2009

Its a key lean startup concept. It has to be found and managed. Open APIs and data-oriented architecture (aka "web 2.0"). For example, I recently created a customer validation exercise around the Lean Startup Workshop. The Lean Startup Intensive is tomorrow at Web 2.0. Yeah, weve got that. Leverage is work, though.

Product Development 88

Product Development Developer San Francisco Product 88

Startup Lessons Learned

OCTOBER 5, 2009

It’s important to invest in good architecture so that your website will scale once customers arrive. If you make that investment, and then customers arrive, and the site stays up, most companies will reward the people who built the architecture and, thus, prevented the scaling problems. Why do they harbor that paranoia?

San Francisco 133

San Francisco Architecture Lean Continuous Deployment 133

Startup Lessons Learned

JULY 13, 2009

Lessons Learned by Eric Ries Monday, July 13, 2009 The Principles of Product Development Flow If youve ever wondered why agile or lean development techniques work, The Principles of Product Development Flow: Second Generation Lean Product Development by Donald G. For example, take the lean dictum of working in small batches.

Product Development 153

Product Development Developer San Francisco Product 153

Startup Lessons Learned

NOVEMBER 29, 2008

Balancing competing objectives is a recurring theme on this blog - its the central challenge of all management decisions. The best candidates have managed to teach me something about a topic I thought I already knew a lot about. This responsibility falls squarely to the hiring manager. Communication.

San Francisco 146

San Francisco Lean Agile Java 146

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 7, 2008

In a few cases, they are clearly smart people in a bad situation, and Ive written about their pain in The product managers lament and The engineering managers lament. I know them right away - we can talk high-level architecture all the way down to the bits-and-bytes of his system. Just change it.

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

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. So far, this is just a summary of what all of us who have attempted to build web-scale architectures considers obvious. Support multiple sharding schemes. Easy to understand.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

SEPTEMBER 8, 2009

Beyond just those who will be hearing about the lean startup for the first time, Im expecting to shake a lot of hands and have a lot of interesting side conversations. Policy makers need to know: regulations designed to manage big-companies actually protect those companies by stifling innovation (and competition) from startups.

DC 90

DC Washington San Francisco SBIR 90

Startup Lessons Learned

SEPTEMBER 22, 2008

Someone has managed to convince themselves that they have to do their big architecture change in one fell swoop. The Lean Startup Intensive is tomorrow at Web 2.0. Case Study: Continuous deployment makes releases n. Amazing lean startup resources Is Entrepreneurship a Management Science? Expo SF (May.

Product Development 68

Product Development Developer San Francisco Product 68

Startup Lessons Learned

JANUARY 30, 2009

Even though some aspects of the product were eventually vindicated as good ones, the underlying architecture suffered from hard-to-change assumptions. Even a great architecture becomes inflexible. The Lean Startup Intensive is tomorrow at Web 2.0. After years of engineering effort, changing these assumptions was incredibly hard.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

JANUARY 28, 2009

The engineering team has decided its reached a breaking point, and is taking several weeks to bring it up to modern standards, including unit tests, getting started with continuous integration , and a new MVC architecture. On the other, they already have a team fully engaged on making their product architecture better.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79