Continuous Deployment Cost Dividend Product Development 
Startup Lessons Learned
MARCH 25, 2010
This is the first post that moves into making specific process recommendations for product development. Hence, cutting corners often paid huge dividends. Labels: product development Speed up or slow down? This is the first post that moves into making specific process recommendations for product development.
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. I owe it originally to lean manufacturing books like Lean Thinking and Toyota Production System. Labels: five whys root cause analysis , product development 11comments: Peter Severin said.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
OCTOBER 19, 2009
"We do not develop a product until we get a paying customer," says Orit Pennington , who co-founded the six-employee company with her husband in 2002. Development time is typically no more than two to three weeks, and it generally takes just a few orders to cover development costs. Read the rest. Read the rest.
Startup Lessons Learned
JULY 2, 2009
Yet in every situation where I have asked, nobody has been tasked with making a realistic estimate, either of the impact of this lack of training or the real costs of the solution. Remember that the cost of the solutions is proportional to the problem caused. Case Study: Continuous deployment makes releases n.
Startup Lessons Learned
JANUARY 28, 2009
Because, unless you are working in an extremely static environment, your product development team is learning and getting better all the time. If thats not a team-wide phenomenon, then its still a form of waste, because everyone has to learn every lesson before it starts paying dividends. Share what you learn. Great post, Eric.
Expert insights. Personalized for you.
141 
Let's personalize your content