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.

Lean 167

Lean Startup Software Engineering Agile 167

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.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

SEPTEMBER 27, 2010

One of the sayings I hear from talented managers in product development is, “good enough never is.&# And, most importantly, it helps team members develop the courage to stand up for these values in stressful situations. Lessons Learned by Eric Ries Monday, September 27, 2010 Good enough never is (or is it?)

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

AUGUST 1, 2009

Also SJ's obsession with better taste (positively) contributes to the overall product development process. There are some good anecdotes about Chief Engineers in the Toyota Product Development Book. Some of these reaffirm that they do indeed validate assumptions through interaction with customers.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

DECEMBER 7, 2008

Sometimes, a great hacker has the potential to grow into the CTO of a company, and in those cases all you need is an outside mentor who can work with them to develop those skills. At the end of the day, the product development team of a startup (large or small) is a service organization. Does this sound familiar?

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

DECEMBER 6, 2008

When youve mastered that, consider adding operations, customer service, marketing, product management, business development - the idea is that when the team needs to get approval or support from another department, they already have an "insider" who can make it happen.

San Francisco 74

San Francisco SCRUM Lean Continuous Deployment 74

www.quora.com

JANUARY 16, 2011

" => I have not bothered to put up a landing page, survey to test customer demand, or done any customer development whatsoever. "Where is the best place to find a rockstar developer to bring it to life?" Ability to sell and evangelize the idea to recruits, press, customers. For your employees?

Developer 42

Developer Technical Review Cofounder Technical Cofounder 42

maplebutter.com

JANUARY 8, 2013

what are the most crucial steps to be taken by a new tech startup when outsourcing major part of the tech to IT firms or outsourcing “product development” eg new social media website project? Near shoring development with your team (ex: your team is based in Canada / India) is cool, but not outsourcing. 1) Hire A’s.

Technical Review 44

Technical Review Startup Cofounder Software Review 44