Startup Lessons Learned

MARCH 16, 2009

Ever since that time, I have struggled to explain how the feedback loop in customer development should interface with the feedback loop in product development. What causes projects like this to fail in traditional software development is that the solution is unknown. What do you do if the problem itself is unknown?

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

NOVEMBER 4, 2008

It is becoming easier and cheaper for companies to bring products to market, leveraging free and open source software , cloud computing, open social data (Facebook, OpenSocial ), and open distribution (AdWords, SEO). Agile software development. Agile allows companies to build higher quality software faster.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

JULY 2, 2009

Labels: five whys root cause analysis , product development 15comments: Anonymoussaid. Furthermore, I think most of what you are suggesting is applicable in companies/ industries that are not software development. Leave your thoughts in a comment. If you’ve tried Five Whys, please share your experiences so far.

San Francisco 164

San Francisco Lean Technical Review Software Review 164

Startup Lessons Learned

FEBRUARY 28, 2009

This builds on a lot of great thinking that has come before, like the agile movements insistence that only the creation of working code counts as progress for a software development team. None of it would have happened if we had plenty of cash, or were content to count our progress by traffic or product development milestones.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

JULY 30, 2009

I thought Id share a little bit of that, too: I’ve been interested in different approaches to software development going back to 1987 when – in my first company Feld Technologies – my partner Dave Jilk and I started talking about “semi-custom software development&# (way ahead of its time).

Lean 68

Lean San Francisco Continuous Deployment DC 68

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 San Francisco Part-Time VPE 94

Startup Lessons Learned

SEPTEMBER 2, 2008

Lessons Learned by Eric Ries Tuesday, September 2, 2008 On deployment My favorite question to ask a software development team is "how do you do a release." Thoughts on scientific product development Lo, my 5 subscribers, who are you? You can tell a lot about a company from their deployment flow. How fast do they iterate?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

JUNE 15, 2009

Why do software developers think this is acceptable? Part of putting this into action is requiring your team to have a very deep understanding of their customers. June 22, 2009 10:07 AM Khris said. Would you buy a car that constantly had to go back to the dealer to be improved? I should think not. Thanks for this.

Continuous Deployment 167

Continuous Deployment Software Review San Francisco Lean 167

Startup Lessons Learned

FEBRUARY 9, 2009

It uses principles of agile software development, open source and web 2.0, The Lean Startup is a practical approach for creating and managing a new breed of company that excels in low-cost experimentation, rapid iteration, and true customer insight. Take a look and let me know what you think.

Lean 68

Lean San Francisco Web Advisory Board 68

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. Thank you so much!)

Agile 60

Agile Lean San Francisco Continuous Deployment 60

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. Take a look and let me know what you think.

San Francisco 74

San Francisco SCRUM Lean Continuous Deployment 74

Startup Lessons Learned

MAY 27, 2009

It uses principles of agile software development, open source and web 2.0, The Lean Startup is a practical approach for creating and managing a new breed of company that excels in low-cost experimentation, rapid iteration, and true customer insight. Take a look and let me know what you think.

Lean 60

Lean Austin San Francisco Startup 60

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. I really enjoyed this article, my first time reading any of your stuff. Will start to pay attention. Great post Eric.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

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

FEBRUARY 10, 2009

You cant make these global efficiency improvements until you get clear about the goal of your development process. That leads to a seemingly-obvious question: what is progress in software development? It would be hard to argue against this product development strategy, in general. If a feature worked, wed keep it.

Continuous Deployment 123

Continuous Deployment San Francisco Software Review Lean 123

Startup Lessons Learned

JANUARY 28, 2009

Its an essential discipline of good software development, especially in startups. Because, unless you are working in an extremely static environment, your product development team is learning and getting better all the time. Labels: agile , product development , Test-driven development 11comments: William Pietri said.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79