Remove Agile Remove CTO Hire Remove Distribution Remove Software
article thumbnail

Lessons Learned: What does a startup CTO actually do?

Startup Lessons Learned

Lessons Learned by Eric Ries Tuesday, September 30, 2008 What does a startup CTO actually do? Often times, it seems like people are thinking its synonymous with "that guy who gets paid to sit in the corner and think technical deep thoughts" or "that guy who gets to swoop in a rearrange my project at the last minute on a whim."

CTO 168
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. Of course, many startups are capital efficient and generally frugal.

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

Lessons Learned by Eric Ries Tuesday, September 2, 2008 Just-In-Time Scalability At my previous company, we pioneered an approach to building out our infrastructure that we called "Just-In-Time Scalability." After all, the worst kind of waste in software development is code to support a use case that never materializes.

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

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. are the parts of the Joel Test I think are most out-of-date. Youd better.

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

Lessons Learned: Test-Driven Development as andon cord

Startup Lessons Learned

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. These tests are written by the engineers themselves, and they must all pass every time. .