Remove Agile Remove Lean Remove SEM Remove Software
article thumbnail

Lessons Learned: The lean startup

Startup Lessons Learned

Lessons Learned by Eric Ries Monday, September 8, 2008 The lean startup Ive been thinking for some time about a term that could encapsulate trends that are changing the startup landscape. After some trial and error, Ive settled on the Lean Startup. I like the term because of two connotations: Lean in the sense of low-burn.

Lean 168
article thumbnail

Lessons Learned: Just-In-Time Scalability

Startup Lessons Learned

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.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Lessons Learned: Customer Development Engineering

Startup Lessons Learned

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

article thumbnail

Lessons Learned: A new version of the Joel Test (draft)

Startup Lessons Learned

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!) Can you make a build in one step? Youd better.

article thumbnail

Lessons Learned: What does a startup CTO actually do?

Startup Lessons Learned

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
article thumbnail

Lessons Learned: Ideas. Code. Data. Implement. Measure. Learn

Startup Lessons Learned

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. Labels: agile , listening to customers 3comments: hauteroute said. Great points Eric.

article thumbnail

On deployment

Startup Lessons Learned

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.