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

SEPTEMBER 2, 2008

We wanted an agile approach that would allow us to build our software architecture as we needed it, without downtime, but also without large amounts of up-front cost. After all, the worst kind of waste in software development is code to support a use case that never materializes. Take a look and let me know what you think.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

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.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

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. Luckily for me, my co-founders eventually prevailed and we went on to build a product that customers actually wanted.

San Francisco 98

San Francisco Continuous Deployment Lean DC 98

Startup Lessons Learned

FEBRUARY 9, 2009

It uses principles of agile software development, open source and web 2.0, ► August (2) SXSW Case Study: SlideShare goes freemium ► July (4) Case Study: kaChing, Anatomy of a Pivot Some IPO speculation Founder personalities and the “first-class man&# th. Case Study: Continuous deployment makes releases n.

Lean 68

Lean San Francisco Web Advisory Board 68

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." You can tell a lot about a company from their deployment flow. After an hour with a team talking dirty about deployment, youll know. How fast do they iterate?

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

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). Lean startups have the ability to use this commodity stack to lower costs and, more importantly, reduce time to market.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

MARCH 16, 2009

What’s worse is that as you grow you’ve probably developed some pretty bad habits as far as setting priorities and strategy: like thinking you’re a genius - just because you got funded - and that genius is what allows you to *know* what the market wants. Case Study: Continuous deployment makes releases n.

Agile 111

Agile Customer Development Developer San Francisco 111

Startup Lessons Learned

SEPTEMBER 27, 2010

I believe this is one reason why the myth of the dictatorial startup founder has such enduring appeal. Lean manufacturing , agile software development , and Theory of Constraints are all examples of this idea in action. I believe this is one reason why the myth of the dictatorial startup founder has such enduring appeal.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

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.

Agile 60

Agile Lean San Francisco Continuous Deployment 60

Startup Lessons Learned

AUGUST 1, 2009

Heres the key quote: Steve Jobs on why Apple doesn’t do market research - Bokardo It’s not about pop culture, and it’s not about fooling people, and it’s not about convincing people that they want something they don’t. Now, I cant speak to what process Steve Jobs uses to get his team to do this market assessment.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

FEBRUARY 22, 2010

Engineers are offenders in this category too, but so is any gender-segregated activity, like an all-female PR or marketing team. Even if men have an innate advantage at software development, the gap would have to be massive in order to explain why startup after startup has an all-male team. Demographic diversity is an indicator.

San Francisco 167

San Francisco Lean Sweden Continuous Deployment 167

Startup Lessons Learned

MAY 27, 2009

It uses principles of agile software development, open source and web 2.0, This will be an in-depth discussion with a handful of entrepreneurs and founders that have been pre-selected. This event is being organized by Manuel Rosso, an EIR at Austin Ventures, and my former collaborator back when he was VP of Marketing at IMVU.

Lean 60

Lean Austin San Francisco Continuous Deployment 60

Startup Lessons Learned

JANUARY 28, 2009

Its an essential discipline of good software development, especially in startups. Fortunately, my co-founders are also engineers and understand the need for some of the stuff I do. Eric - There is definitely a business/marketing analog to exactly this situation that happens a lot too. Balance is important.

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

Startup Lessons Learned

DECEMBER 7, 2008

Even if, in a previous life, you were a world expert in some functional specialty, like in-depth market research or scalable systems design, the compressed timeline of a startup makes it irrelevant. Our CTO is the CEO himself, but he lacks the understanding of the new software development processes and the new technologies.

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. Case Study: Continuous deployment makes releases n.

San Francisco 74

San Francisco SCRUM Lean Continuous Deployment 74

Startup Lessons Learned

JULY 2, 2009

These problems can be anything: development mistakes, site outages, marketing program failures, or even internal missed schedules. Furthermore, I think most of what you are suggesting is applicable in companies/ industries that are not software development. Case Study: Continuous deployment makes releases n.

San Francisco 164

San Francisco Lean Technical Review Software Review 164