Startup Lessons Learned

SEPTEMBER 15, 2008

But by taking advantage of open source, agile software, and iterative development, lean startups can operate with much less waste. So far, I have found "lean startup" works better with the entrepreneurs Ive talked to than "agile startup" or even "extreme startup.") Of course, many startups are capital efficient and generally frugal.

Lean 168

Lean San Francisco Startup Continuous Deployment 168

Steve Blank

MARCH 18, 2011

Dot.com Bubble ( 1995-2000): “ Anything goes” as public markets clamor for ideas, vague promises of future growth, and IPOs happen absent regard for history or profitability. With Netscape’s IPO , there was suddenly a public market for companies with limited revenue and no profit. The New Bubble : (2011 – 2014): Here we go again…. (If

Internet 334

Internet IPO Silicon Valley Agile 334

Startup Lessons Learned

SEPTEMBER 8, 2008

Lessons Learned by Eric Ries Monday, September 8, 2008 Waves of technology platforms I still remember the first time I switched to LAMP. That startup didnt turn out so well, but not for lack of technology. I was building a new startup in 1999, and wanted to do it right. No departments The Five Whys for Startups (for Harvard Business R.

San Francisco 68

San Francisco Technology Continuous Deployment Lean 68

Startup Lessons Learned

SEPTEMBER 30, 2008

What does your Chief Technology Officer do all day? When Ive asked mentors of mine who have worked in big companies about the role of the CTO, they usually talk about the importance of being the external face of the companys technology platform; an evangelist to developers, customers, and employees. I mean, have you seen other people?

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

The Next Web

JANUARY 24, 2014

We have three universities in the top 100 of the Shanghai ranking for engineering and technology. Think of Werner Vogels (CTO of Amazon), Guido van Rossem (founder of Python programming language and senior engineer at Dropbox) or the more senior Gerard Kleisterlee (chairman of Vodafone).

Netherlands 143

Netherlands Technical Review Stock Silicon Valley 143

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. You can also download our presentation, " Just-In-Time Scalability: Agile Methods to Support Massive Growth." Expo SF (May. Seth Godin: How often should you publish?

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

JANUARY 30, 2009

Build a world-class technology platform, with patent-pending algorithms and the ability to scale to millions of simultaneous users. After years of engineering effort, changing these assumptions was incredibly hard. This is why agility is such a prized quality in product development. Ship it when its done, not a moment before.

San Francisco 150

San Francisco Lean Agile Continuous Deployment 150

Startup Lessons Learned

NOVEMBER 29, 2008

Finding great engineers is hard; figuring out whos good is even harder. The six key attributes spell ABCDEF: Agility. When talking about their past experience, candidates with agility will know why they did what they did in a given situation. I have found this quite rare in engineers.

San Francisco 146

San Francisco Lean Agile Java 146

Startup Lessons Learned

OCTOBER 4, 2008

He previously co-founded and served as Chief Technology Officer of IMVU. 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. An engineer who can talk intelligently about gender! hope to hear from you.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

Startup Lessons Learned

JUNE 22, 2009

Each has its own iterative process: customer development and agile development respectively. As the CTO/VP Engineering, I was the worst offender. That means that I (and other engineers) were able to participate in the problem team discussions. Thats why its so essential to have a co-equal problem team. Context matters.

San Francisco 167

San Francisco Lean Continuous Deployment Agile 167

Startup Lessons Learned

NOVEMBER 4, 2008

Boyd emphasized the importance of agility in combat: "the key to victory is to be able to create situations wherein one can make appropriate decisions more quickly than ones opponent." As Ive written previously , lean startups are built upon three main trends: Technology commoditization. Agile software development.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

SEPTEMBER 10, 2008

Lessons Learned by Eric Ries Wednesday, September 10, 2008 Smarticus — 10 things you could be doing to your code right now Smarticus — 10 things you could be doing to your code right now A great checklist of techniques and tools for making your development more agile, written from a Rail perspective. Expo SF (May.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

Startup Lessons Learned

AUGUST 3, 2009

Refreshing to finally see lean and agile thinking emerge in product/business-floors and not only in technology. ► 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. Thank you.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Startup Lessons Learned

JUNE 17, 2010

I was an engineer on the engineering team. For one, the engineers consider the artists stupid; the artists consider the engineers arrogant. The engineering team would then build that feature, mimicking the UI as close as they could using the current primitives supported by the system. The meeting was tense.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

SEPTEMBER 22, 2008

I break the answer to that question down into three engines: Viral - this is the business model identified in the presentation as "Get Users." Thats why eBay advertises on search engines, and Facebook doesnt. Labels: search engine marketing 0comments: New comments are not allowed. Thats where Id like to pick up the discussion.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

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. Every time an engineer checks in code, they are batching up a certain amount of work. Sounds very similar to agile development which is the way. February 21, 2009 7:39 AM Rocky1138 said.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

Startup Lessons Learned

SEPTEMBER 13, 2008

Trying to answer that question at IMVU led me to discover Google AdWords and the world of search engine marketing. You declare how much someone clicking an advertisement is worth to you, and then the search engine does its best to get you as many clicks as it can at that price. Labels: search engine marketing 4comments: Tauya said.

SEM 164

SEM San Francisco Lean Continuous Deployment 164

Startup Lessons Learned

JULY 29, 2009

The human tendency to moralize about debt affects engineers, too. I hope to show why lean and agile techniques actually reduce the negative impacts of technical debt and increase our ability to take advantage of its positive effects. Side-effects that reduce agility are the most damaging symptoms of technical debt.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

SEPTEMBER 10, 2008

I know plenty of people who prefer more advanced source control system, but my belief is that many agile practices diminish the importance of advanced features like branching. At IMVU , our engineering team accumulated thousands upon thousands of tests, and we had a build cluster (using BuildBot ) that ran them. Youd better.

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

Startup Lessons Learned

AUGUST 1, 2009

Beyond Apple, we can find examples of the Steve Jobs character at Toyota, in the form of the Chief Engineer. There are some good anecdotes about Chief Engineers in the Toyota Product Development Book. So I don't think the Apple experience should be used to discount lean, agile, or customer development-type approaches.

San Francisco 166

San Francisco Lean Continuous Deployment DC 166

Startup Lessons Learned

SEPTEMBER 2, 2008

Labels: agile , listening to customers 3comments: hauteroute said. ► 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. Split-test experiments that go on forever? Great points Eric.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

OCTOBER 28, 2008

Now there was nothing wrong with their analysis: anyone who invents a technology as sophisticated as The Transformers is definitely going to make a lot of money. Turns out, they were incredibly well-credentialed graduate students who had, in fact, developed some interesting new robotics technology. whos on the engineering team?

San Francisco 128

San Francisco Lean Continuous Deployment DC 128

Startup Lessons Learned

AUGUST 2, 2008

Lessons Learned by Eric Ries Saturday, August 2, 2008 Paul Graham on fundraising I have found no better primer on the current realities of starting a new technology company in a startup hub like Silicon Valley than Paul Grahams essays. but rest assured they would be. No departments The Five Whys for Startups (for Harvard Business R.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

DECEMBER 7, 2008

In a few cases, they are clearly smart people in a bad situation, and Ive written about their pain in The product managers lament and The engineering managers lament. Its common to find a hacker at the heart of almost any successful technology company. Hire a CTO or VP Engineering. Just change it. Does this sound familiar?

Software Review 94

Software Review Technical Review Part-Time VPE San Francisco 94

Startup Lessons Learned

SEPTEMBER 1, 2008

In almost all Agile Development systems, thousands of automated tests are run against every change to the software. These tests are written by the engineers themselves, and they must all pass every time. Automated tests make defects visible. The visionary’s lament The Superbowl ad test Lo, my 57692 subscribers, who are you?

San Francisco 68

San Francisco Developer Continuous Deployment DC 68

Startup Lessons Learned

NOVEMBER 8, 2008

This theory has become so influential that I have called it one of the three pillars of the lean startup - every bit as important as the changes in technology or the advent of agile development. Very few startups fail for lack of technology. They almost always fail for lack of customers. Expo SF (May.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

SEPTEMBER 12, 2008

► 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. The visionary’s lament The Superbowl ad test Lo, my 57692 subscribers, who are you? Expo SF (May. Seth Godin: How often should you publish?

Audience 119

Audience San Francisco Continuous Deployment Lean 119

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). Expo SF (May.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

JANUARY 7, 2010

So you can imagine how I expected some skepticism when pitching ideas about technology innovation to, say, the U.S. So you can imagine how I expected some skepticism when pitching ideas about technology innovation to, say, the U.S. Read the rest at The Conversation - Harvard Business Review. Expo SF (May.

San Francisco 119

San Francisco Management Continuous Deployment Lean 119

Startup Lessons Learned

FEBRUARY 9, 2009

It uses principles of agile software development, open source and web 2.0, and lean manufacturing to guide the creation of technology businesses that create disruptive innovation. Hey Someone else who is extending the agile/lean approach beyond just developing software. February 9, 2009 7:45 PM Joseph Flahiff said. Expo SF (May.

Lean 68

Lean San Francisco Web Advisory Board 68

www.vccafe.com

MARCH 11, 2013

Every startup faces multiple choices and decisions when it comes to technology. Firebase : Are all your developers front-end engineers? Google Custom Search Engine. Google App Engine. Ad Serving Technology. Search Engine Optimization Tools. Hundreds of startups featured since 2005, will yours be next?

Software Review 53

Software Review Technical Review Startup 53

Startup Lessons Learned

SEPTEMBER 14, 2008

Later, when the company was much larger, we had everyone on our engineering team agree to sit in on one usability test every month. It wasnt a huge time commitment, but it meant that every engineer was getting regular contact with an actual customer, which was invaluable. Expo SF (May. Seth Godin: How often should you publish?

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Lessons Learned

SEPTEMBER 5, 2008

► 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. The visionary’s lament The Superbowl ad test Lo, my 57692 subscribers, who are you? Expo SF (May. Seth Godin: How often should you publish?

Open Source 107

Open Source San Francisco Continuous Deployment Lean 107

Startup Lessons Learned

SEPTEMBER 2, 2008

Do the engineers understand what they are building? ► 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. Processes are always deteriorating or self-regulating. Do they measure? Expo SF (May.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Cracking the Code

SEPTEMBER 19, 2017

12 cloud IPOs in the past 2 years: One from Europe SaaS companies are thriving in the public markets, with their aggregated market cap grew 350% since 2011, and 12 cloud companies going public in the past 24 months. Out of the 12 IPOs, Mimecast is the only company from Europe. in the US, $2.6B in Europe and $0.9B

Europe 83

Europe Cloud API 83

Startup Lessons Learned

NOVEMBER 17, 2008

For example, should we invest a week of engineering time into making our website more failure-proof (which were pretty sure will pay off right away) or into experimenting with a new technology (that might pay off in months, years, or never)? The visionary’s lament The Superbowl ad test Lo, my 57692 subscribers, who are you?

San Francisco 79

San Francisco Lean Continuous Deployment DC 79

Startup Lessons Learned

JANUARY 15, 2010

And when companies pursue sustaining innovations — like a product line extension or a new technology designed to serve an existing customer segment — this procedure makes complete sense. They are long-term bets on the development of a new line of business, a new technology platform, or the creation of a new market.

Hockey Stick 105

Hockey Stick San Francisco Entrepreneur Lean 105