Agile Architecture Product Development SEM 
Startup Lessons Learned
SEPTEMBER 22, 2008
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.
Startup Lessons Learned
SEPTEMBER 2, 2008
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.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
SEPTEMBER 30, 2008
If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? That means knowing whats written and whats not, what the architecture can and cant support, and how long it would take to build something new. Labels: product development 15comments: mukund said.
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. Ive attempted to embed the relevant slides below. Expo SF (May.
Startup Lessons Learned
SEPTEMBER 8, 2008
You dont need to invent a new architecture, and you dont need to even build your architecture up-front. You can turn your entire application infrastructure investment into a pay-as-you-go variable cost, and bring new products to market at speeds an order of magnitude faster than just 10 years ago. yeah, its awesome.
Expert insights. Personalized for you.
68 
Let's personalize your content