Startup Lessons Learned
SEPTEMBER 7, 2008
Lessons Learned by Eric Ries Sunday, September 7, 2008 Customer Development Engineering Yesterday, I had the opportunity to guest lecture again in Steve Blank s entrepreneurship class at the Berkeley-Columbia executive MBA program. Its a nice complement on the product engineering side to his customer development methodology.
Startup Lessons Learned
NOVEMBER 6, 2008
Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective. They work hard to keep their house in order at all times, and there are strict rules and guidelines in place that prevent engineers and teams from doing things their own way.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Startup Lessons Learned
OCTOBER 4, 2008
In 2007, BusinessWeek named Ries one of the Best Young Entrepreneurs of Tech and in 2009 he was honored with a TechFellow award in the category of Engineering Leadership. I help lead the Engineering Leadership SIG at SDForum and wonder if you would be interested in speaking to our group about lean starups. hope to hear from you.
Startup Lessons Learned
AUGUST 8, 2009
I thought a good place to start was with the origins of the idea that "software design" should be considered a discipline in its own right, on par with computer science, software engineering, and computer programming. Great engineers see it and smile. This is called set-based concurrent engineering (SBCE). [1]
Startup Lessons Learned
OCTOBER 16, 2013
We work in prototypically four-week iterations, with quality engineers and software developers working in close collaboration. Here''s the simplest form of that cycle: Week -1 - Planning/End-of-Cycle - Software engineers are planning: writing specifications, doing light prototyping, and experimentation.
Startup Lessons Learned
NOVEMBER 29, 2008
Finding great engineers is hard; figuring out whos good is even harder. For software engineers, I think this absolutely has to be a programming problem solved on a whiteboard. I have found this quite rare in engineers. Many of us engineers are strong introverts, without fantastic people skills.
Startup Lessons Learned
DECEMBER 8, 2008
Theoretically, i can visualize the Continuous Integration as RAD ( Rapid action development) along with iterative method, which we used to study in Software Engineering's Process model. We, the s/w engineer have to rethink about the solution, the code which need to change, which would reflect the right change.
Expert insights. Personalized for you.
131 
Let's personalize your content