Startup Lessons Learned
NOVEMBER 14, 2013
We asked him a few questions to learn about continuous delivery, why it’s useful, and what engineers and management need to do to implement it. LSC: One of the biggest fears people have about a continuous deployment environment is that it introduces more risk to engineering. Thus we reduce the risk of deployments.
Startup Lessons Learned
JULY 5, 2010
While the customer development framework of Four Steps is universally relevant, The Entrepreneur’s Guide updates its practices for modern startups. While the customer development framework of Four Steps is universally relevant, The Entrepreneur’s Guide updates its practices for modern startups. Want to learn more about me?
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
SEPTEMBER 22, 2008
is an elegant way to model any service-oriented business: Acquisition Activation Retention Referral Revenue We used a very similar scheme at IMVU, although we werent lucky enough to have started with this framework, and so had to derive a lot of it ourselves via trial and error. Case Study: Continuous deployment makes releases n.
Startup Lessons Learned
JANUARY 15, 2010
This whole framework breaks down when teams confront entrepreneurial situations in which theyre trying to build something new under conditions of extreme uncertainty. This whole framework breaks down when teams confront entrepreneurial situations in which theyre trying to build something new under conditions of extreme uncertainty.
Startup Lessons Learned
MARCH 29, 2010
Tactics were discussed out of context, and there wasnt an overarching framework for figuring out what works for what kinds of companies, industries, and stages of growth. Doesnt the communication overhead of a large team lead to chaos of overlapping experiments and continuously-deployed bugs?" "If Is design important to lean startups?
Startup Lessons Learned
JUNE 22, 2009
A good example is Paypal realizing that their customers were gravitating to the email-payments part of their original solution, and ignoring the complex PDA-based cryptography solution. Instead of these dead-ends, use the problem and solution team framework and then: pivot, dont jump. Case Study: Continuous deployment makes releases n.
Startup Lessons Learned
SEPTEMBER 10, 2008
But if you want to practice rapid deployment, you need to be able to deploy that build in one step as well. If you want to do continuous deployment, youd better be able to certify that build too, which brings us to. For more on continuous deployment, see Just-in-time Scalability. Can you make a build in one step?
Expert insights. Personalized for you.
162 
Let's personalize your content