Agile Continuous Deployment Metrics Silicon Valley 
Startup Lessons Learned
NOVEMBER 6, 2008
Lessons Learned by Eric Ries Thursday, November 6, 2008 Steveys Blog Rants: Good Agile, Bad Agile I thought Id share an interesting post from someone with a decidedly anti-agile point of view. Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective.
Startup Lessons Learned
APRIL 25, 2011
It may be hard to remember that there was a time when people in the agile software development community thought Lean Startup was incompatible with agile practices. And, most importantly, the Lean Startup idea is starting to take root in industries and contexts very different from it’s Silicon Valley roots.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
AUGUST 26, 2009
Its easy to take Silicon Valley for granted. Ive written a little bit about the origins of Silicon Valley because I think its important for us to understand how we got here in order to make sure we preserve what is best about our community. Case Study: Continuous deployment makes releases n. Expo SF (May.
Startup Lessons Learned
AUGUST 2, 2008
Lessons Learned by Eric Ries Saturday, August 2, 2008 Paul Graham on fundraising I have found no better primer on the current realities of starting a new technology company in a startup hub like Silicon Valley than Paul Grahams essays. Case Study: Continuous deployment makes releases n. but rest assured they would be. .
Startup Lessons Learned
JANUARY 30, 2009
This is why agility is such a prized quality in product development. As with many Silicon Valley failures, a flawless PR launch turned into a flawed customer acquisition strategy. Departments were built and were even metrics-driven. But there was no feedback loop to help the company find the right metrics to focus on.
Startup Lessons Learned
NOVEMBER 13, 2008
Because five whys kept turning up a few key metrics that were hard to set static thresholds for, we even had a dynamic prediction algorithm that would make forecasts based on past data, and fire alerts if the metric ever went out of its normal bounds. Wed never heard of five whys, and we had plenty of "agile skeptics" on the team.
Startup Lessons Learned
NOVEMBER 4, 2008
Boyd emphasized the importance of agility in combat: "the key to victory is to be able to create situations wherein one can make appropriate decisions more quickly than ones opponent." Agile software development. Agile allows companies to build higher quality software faster. This speeds up the Ideas-Code-Data feedback loop.
Expert insights. Personalized for you.
76 
Let's personalize your content