Remove Architecture Remove Continuous Deployment Remove Customer Development Remove Non-Compete
article thumbnail

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

Startup Lessons Learned

And as Kapor himself points out, the core ideas have even older origins: The Roman architecture critic Vitruvius advanced the notion that well-designed buildings were those which exhibited firmness, commodity, and delight. Customer Development is itself an example of SBCE. We owe a lot to this seminal document.

article thumbnail

The Principles of Product Development Flow

Startup Lessons Learned

But it goes beyond that, including techniques for improving the economics of product development. Reinertsen weaves together ideas from lean manufacturing, maneuver warfare, queuing theory, and even the architecture of computer operating systems and the Internet. Case Study: Continuous deployment makes releases n.

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

article thumbnail

What would you want to tell Washington DC about startups?

Startup Lessons Learned

I started my last company with 100% off-shore resources because I could never have completed Customer Development at a reasonable cost of money or regulatory burden had I employed US Citizens. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup?

DC 90