Continuous Deployment Design Employee Software Development 
Startup Lessons Learned
OCTOBER 16, 2013
We work in prototypically four-week iterations, with quality engineers and software developers working in close collaboration. This finally bit us after a four month stint of development blew through its testing schedule by a factor of four: two scheduled weeks turned into two months before the product reached stability.
Startup Lessons Learned
SEPTEMBER 27, 2010
This is precisely the dilemma that the doctrine of minimum viable product is designed to solve. When people start using quality, reliability, or design as an excuse to delay, it used to make me nervous, even when these suggestions were well intentioned. Rules of thumb can be infuriatingly unhelpful. And it’s really hard.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
OCTOBER 4, 2008
Although Catalyst folded with the dot-com crash, Ries continued his entrepreneurial career as a Senior Software Engineer at There.com, leading efforts in agile software development and user-generated content. Case Study: Continuous deployment makes releases n. November 25, 2009 9:54 AM Danny Wong said.
Startup Lessons Learned
AUGUST 1, 2009
My guess is they have lots of people constantly working on interesting new tools for their designers to play with. Discover whats in customers heads, and tackle problems where design is a differentiator. Those new capabilities must translate into a constant stream of prototypes - most of which turn out to be utterly bad ideas.
Startup Lessons Learned
MARCH 25, 2009
Agile Vancouver : Lean Development for Lean Times On Tuesday April 21st, we are hosting an afternoon event on the application of Lean Principles to software development. This workshop brings together leading thinkers from Lean Production and Lean software. Case Study: Continuous deployment makes releases n.
Startup Lessons Learned
MARCH 16, 2009
In the case of C3, that was to run payroll for 87,000 employees, who were presumably receiving payroll before the project began. What causes projects like this to fail in traditional software development is that the solution is unknown. Case Study: Continuous deployment makes releases n. Thats pretty clear.
Startup Lessons Learned
JULY 2, 2009
For example, I often cite a real example of a problem that has as its root cause a new employee who was not properly trained. I pick that example on purpose, for two reasons: 1) most of the companies I work with deal with this problem and yet 2) almost none of them have any kind of training program in place for new employees.
Expert insights. Personalized for you.
167 
Let's personalize your content