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
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.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
SEPTEMBER 10, 2008
If you want to do continuous deployment, youd better be able to certify that build too, which brings us to. Daily builds are giving way to true continuous integration, in which every checkin to the source control system is automatically run against the full battery of automated tests. Do you make daily builds?
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.
Startup Lessons Learned
AUGUST 8, 2009
I thought a good place to start was with the origins of the idea that "software design" should be considered a discipline in its own right, on par with computer science, software engineering, and computer programming. Great engineers see it and smile. This is called set-based concurrent engineering (SBCE). [1]
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?
Expert insights. Personalized for you.
162 
Let's personalize your content