Remove Agile Remove Continuous Deployment Remove Customer Development Remove Database
article thumbnail

Lessons Learned: A new version of the Joel Test (draft)

Startup Lessons Learned

I know plenty of people who prefer more advanced source control system, but my belief is that many agile practices diminish the importance of advanced features like branching. But if you want to practice rapid deployment, you need to be able to deploy that build in one step as well. Do you have a bug database? Youd better.

article thumbnail

Lessons Learned: What does a startup CTO actually do?

Startup Lessons Learned

If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? And what about if deployment takes forever? Massive proprietary databases? The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? I dont think so.

CTO 168
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: Lean hiring tips

Startup Lessons Learned

They maintain a huge database of passive candidates, by offering to pay them when they interview. Particularly the Continuous Deployment and Split testing posts. The Entrepreneur’s Guide to Customer Development ► June (3) What is a startup? Case Study: Continuous deployment makes releases n.

Lean 140
article thumbnail

Lessons Learned: The engineering manager's lament

Startup Lessons Learned

As I evolved my thinking, I started to frame the problem this way: How can we devise a product development process that allows the business leaders to take responsibility for the outcome by making conscious trade-offs? When I first encountered agile software techniques, in the form of extreme programming , I thought I had found the answer.

article thumbnail

Lessons Learned: Inc Magazine on Minimum Viable Product (and a.

Startup Lessons Learned

But instead of spending the time and money to develop products on spec, TPGTEX creates mocked-up webpages that list the features of a potential new product -- such as a system for making radio-frequency identification, or RFID, labels -- along with its price. The key ideas are customer development , the pivot , MVP, and root cause analysis.

article thumbnail

Lean Startup webcast post-game

Startup Lessons Learned

LIKED: Y startups fail, cont deployment vs waterfall vs agile, small batches & learn fr biz metrics #leanstartup As concise a summary as Ive ever seen. You mentioned as many as 50 deployments a day to production after successful local continuous integration. Case Study: Continuous deployment makes releases n.

Lean 60
article thumbnail

Lessons Learned: Five Whys

Startup Lessons Learned

Wed never heard of five whys, and we had plenty of "agile skeptics" on the team. By the time we started doing continuous integration, we had tens of thousands of lines of code, all not under test coverage. It seems your cluster architecture is one of the key architectural constraints making continuous deployment possible.