Remove Agile Remove Product Development Remove SEM Remove Software
article thumbnail

Thoughts on scientific product development

Startup Lessons Learned

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.

article thumbnail

Lessons Learned: The lean startup

Startup Lessons Learned

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 is an application of Lean Thinking.

Lean 168
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: 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.

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?

article thumbnail

How to Build Robust User Personas in Under a Month

ConversionXL

They can be utilized across teams— UX , CRO, social media, SEM, SEO , etc., The first, according to Dr. David Travis at UserFocus , was agile development : Dr. Teams were savvy enough to know that fully formed, completed descriptions of users are an impossibility at the early stages of design.

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?

article thumbnail

Lessons Learned: Throwing away working code

Startup Lessons Learned

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. We picked those numbers by counting up the numbers of friends, family, and relatives we thought we could cajole into buying our early product.