David Teten
OCTOBER 1, 2015
Customer development would be reduced to a single person exercise that could be repeated in parallel dozens of times over, ultimately yielding 30+ companies a year. Second, the company must eventually own the product development and maintenance functions in-house. Our model at Casual Corp.
Startup Lessons Learned
SEPTEMBER 30, 2008
Own the development methodology - in a traditional product development setup, the VP Engineering or some other full-time manager would be responsible for making sure the engineers wrote adequate specs, interfaced well with QA, and also run the scheduling "trains" for releases. Labels: product development 15comments: mukund said.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
OCTOBER 5, 2009
If we’re practicing continuous deployment, we can be confident that we’ll be able to rush an emergency fix into production without risking introducing further problems. If not, maybe an investment in that direction would be more warranted. If not, maybe an investment in that direction would be more warranted.
Startup Lessons Learned
SEPTEMBER 11, 2009
I agree that listening and communicating is a key to success, but customer development can only do so much. There was also a litany of errors made in determining which developers had in fact passed UFI products into the catalog warranting their punishment. Eric September 13, 2009 11:32 AM Joel Andren said.
Expert insights. Personalized for you.
60 
Let's personalize your content