Continuous Deployment Development Team Review Naming 
Startup Lessons Learned
FEBRUARY 20, 2009
Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. The batch size is the unit at which work-products move between stages in a development process. Take the example of a design team prepping mock-ups for their development team.
Startup Lessons Learned
NOVEMBER 8, 2008
Our goal in product development is to find the minimum feature set required to get early customers. In order to do this, we have our customer development team work hard to find a market, any market, for the product as currently specified. Case Study: Continuous deployment makes releases n. 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
But we were cutting corners in the development methodology as well as in the code, in the name of increased speed. Most of the other processs changes - mandatory design reviews (prelimninary, critical, etc), - documenting all our procedures, and so on - were to support those two factors. And projects dont have quality per se.
Startup Lessons Learned
JULY 13, 2009
It moves at a rapid clip, each argument backed up with the relevant math and equations: marginal profit , Littles law , Markov processes , probability theory , you name it. Its goal is to help us recognize that every artifact of our product development process is really just a proxy variable. Wow, great review!
Expert insights. Personalized for you.
161 
Let's personalize your content