Remove Continuous Deployment Remove Cost Remove Development Team Review Remove Naming
article thumbnail

Lessons Learned: Work in small batches

Startup Lessons Learned

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.

article thumbnail

Lessons Learned: What is customer development?

Startup Lessons Learned

There are three fundamental situations that change what your company needs to do: creating a new market (the original Palm), bringing a new product to an existing market (Handspring), and resegmenting an existing market (niche, like In-n-Out Burger; or low-cost, like Southwest Airlines). Case Study: Continuous deployment makes releases n.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Lessons Learned: The engineering manager's lament

Startup Lessons Learned

But we were cutting corners in the development methodology as well as in the code, in the name of increased speed. I now believe that the "pick two" concept is fundamentally flawed, and that lean startups can achieve all three simultaneously: quickly bring high-quality software to market at low cost.

article thumbnail

The Principles of Product Development Flow

Startup Lessons Learned

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. Second, what is the cost of these queues?