Remove Agile Remove Continuous Deployment Remove Design Remove Non-Compete
article thumbnail

Revisiting the Software Design Manifesto (and what's changed since.

Startup Lessons Learned

Lessons Learned by Eric Ries Saturday, August 8, 2009 Revisiting the Software Design Manifesto (and whats changed since then) My recent article on technical debt and its positive uses generated a fair bit of controversy. The argument itself got me thinking a lot about design and its role in building products.

article thumbnail

Lessons Learned: A hierarchy of pitches

Startup Lessons Learned

Its different from selling a product, because it is not part of our regular business practice, is not something that relates to our core competence, and tends not to happen in a repeatable and scalable way. Ill exclude those non- lean startups who basically exist for the purpose of raising bigger and bigger sums of money. Expo SF (May.

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: Validated learning about customers

Startup Lessons Learned

Their product development team is hard at work on a next-generation product platform, which is designed to offer a new suite of products – but this effort is months behind schedule. And yet their numbers continue to grow, month after month. This approach is fundamentally non-scalable. Go on an agile diet quickly.

Customer 167
article thumbnail

The Principles of Product Development Flow

Startup Lessons Learned

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. Product development deals in designs, which are fundamentally intangible.

article thumbnail

Lessons Learned: Five Whys

Startup Lessons Learned

His book Toyota Production System: Beyond Large-Scale Production is a fascinating read, even though its decidedly non-practical. Hes a new employee, and he was not properly trained in TDD So far, this isnt much different from the kind of analysis any competent operations team would conduct for a site outage. Expo SF (May.

article thumbnail

Lessons Learned: The metrics and levers of engagement.

Startup Lessons Learned

The solution for app developers caught in this vicious cycle is to develop competency in positioning. I would bet (although I don't have the data) that for normal (non-hyper-addict) Facebook users, the time between logins is strongly correlated with the number of high-quality notifications they receive. So, in summary: 1.

Metrics 88
article thumbnail

What would you want to tell Washington DC about startups?

Startup Lessons Learned

Policy makers need to know: regulations designed to manage big-companies actually protect those companies by stifling innovation (and competition) from startups. You can see the design of the program here. Case Study: Continuous deployment makes releases n. September 8, 2009 6:25 PM dbsaid. conference attendees.

DC 90