Continuous Deployment Development Team Review Engineer Metrics 
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. The batch size is the unit at which work-products move between stages in a development process. Every time an engineer checks in code, they are batching up a certain amount of work.
Startup Lessons Learned
OCTOBER 20, 2008
Lessons Learned by Eric Ries Monday, October 20, 2008 The engineering managers lament I was inspired to write The product managers lament while meeting with a startup struggling to figure out what had gone wrong with their product development process. This engineering manager is a smart guy, and very experienced.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
OCTOBER 16, 2013
We work in prototypically four-week iterations, with quality engineers and software developers working in close collaboration. But we couldn''t have identified this without having clear metrics (that high bug count) to assess our development process. It wasn’t always this way.
Startup Lessons Learned
JULY 13, 2009
If we showed the Toyota Production System to an Internet protocol engineer, it is likely that he would remark, "That is a tail-dropping FIFO queue. If engineers want their personal tests to get high priority, their best strategy is to add them to this large, high-priority test package. Wow, great review!
Startup Lessons Learned
OCTOBER 5, 2008
I met one recently that is working on a really innovative product, and the stories I heard from their development team made me want to cringe. The product manager was clearly struggling to get results from the rest of the team. Labels: product development 8comments: Vincent van Wylick said. Frustration is mounting.
Startup Lessons Learned
JUNE 8, 2009
Lessons Learned by Eric Ries Monday, June 8, 2009 Datablindness Most of us are swimming in a sea of data about our products, companies, and teams. That’s because many of our reports feed us vanity metrics: numbers that make us look good but don’t really help make decisions. Too much of this data is non- actionable.
Startup Lessons Learned
NOVEMBER 29, 2008
Finding great engineers is hard; figuring out whos good is even harder. The technical interview is at the heart of these challenges when building a product development team, and so I thought it deserved an entire post on its own. I have found this quite rare in engineers. Thats OK, were not trying to hire a therapist.
Expert insights. Personalized for you.
161 
Let's personalize your content