Startup Lessons Learned

JANUARY 18, 2010

Lessons Learned by Eric Ries Monday, January 18, 2010 Case Study: Continuous deployment makes releases non-events The following is a case study of one entrepreneurs transition from a traditional development cycle to continuous deployment. Continuous Deployment is Continuous Flow applied to software.

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

Startup Lessons Learned

FEBRUARY 22, 2010

Two others – that each team member give their input independently and that the results be objectively aggregated – are also key parts of building a meritocracy. I have personally taught many “non-technical&# people to program – graphic designers, QA folks, even artists and animators.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

Startup Lessons Learned

FEBRUARY 22, 2009

But aggregated across many schools, there are thousands or tens of thousands of them. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica. Two Ways to Hold Entrepreneurs Accountable (for Ha.

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

DECEMBER 14, 2009

In an ecosystem, each participant acts according to its own imperatives, but these selfish actions have an aggregate effect. I had a lot of use for this concept back when I worked on game design and virtual worlds. Constructing a working business model is a form of ecosystem design. And this is true outside of games.

Customer 156

Customer San Francisco Viral Lean 156

Startup Lessons Learned

JANUARY 4, 2009

Sharding for startups To support a single partitioning scheme is easy, especially if you design for it from the start. It also doesnt make sense to design your app for scalability from the start, since you may have to create many iterations before you find a version that requires any scalability at all. 21comments: Imran said.

San Francisco 151

San Francisco Architecture Startup Database 151

Startup Lessons Learned

APRIL 14, 2009

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. Case Study: Continuous deployment makes releases n.

Customer 167

Customer San Francisco Lean Hockey Stick 167

Startup Lessons Learned

JUNE 5, 2009

It’s entirely possible for the startup to be a massive success without having large aggregate numbers, because the startup has succeeded in finding a passionate, but small, early adopter base that has tremendous per-customer behavior. Case Study: Continuous deployment makes releases n.

San Francisco 102

San Francisco Lean Continuous Deployment Startup 102