Continuous Deployment Development Team Review Information Metrics 
Startup Lessons Learned
JUNE 8, 2009
Lessons Learned by Eric Ries Monday, June 8, 2009 Datablindness Most of us are swimming in a sea of data about our products, companies, and teams. That’s because many of our reports feed us vanity metrics: numbers that make us look good but don’t really help make decisions. Too much of this data is non- actionable.
Startup Lessons Learned
NOVEMBER 8, 2008
For the rest of us, we need to get some facts to inform and qualify our hypotheses ("fancy word for guesses") about what kind of product customers will ultimately buy. Our goal in product development is to find the minimum feature set required to get early customers. Lots of good usable information. This is a common mistake.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
OCTOBER 20, 2008
I explained it to people this way: agile lets you make the trade-offs visible to whole company, so that they can make informed choices. By shipping software early, you give them continuous feedback about how it well its working. Case Study: Continuous deployment makes releases n. And projects dont have quality per se.
Startup Lessons Learned
JULY 13, 2009
He shows how the actions of people inside traditional systems are motivated by their rational assessment of their own economics. Reinertsen does not speak about startups specifically - his book is meant to speak broadly to product development teams across industries and sectors.
Startup Lessons Learned
OCTOBER 16, 2013
But we couldn''t have identified this without having clear metrics (that high bug count) to assess our development process. As Shutterstock has grown, there are a few key elements to our continued development speed: Small, autonomous teams: The more a team can do on their own, the faster they can go.
Expert insights. Personalized for you.
84 
Let's personalize your content