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. Just what is the CTO supposed to do?

CTO 168

CTO Fractional CTO CTO Hire Technical Review 168

Startup Lessons Learned

SEPTEMBER 2, 2008

Labels: agile , continuous deployment 1 comments: timothyfitz 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. Case Study: Continuous deployment makes releases n.

San Francisco 94

San Francisco Continuous Deployment Agile Lean 94

Startup Lessons Learned

SEPTEMBER 7, 2008

Labels: agile , continuous deployment , customer development , events , listening to customers , slides 3comments: Sean Murphy 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.

Customer Development 131

Customer Development Engineer San Francisco Developer 131

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. Instead, we do everything possible to validate the founders belief.

Customer Development 168

Customer Development Developer San Francisco Customer 168

Startup Lessons Learned

OCTOBER 4, 2008

He previously co-founded and served as Chief Technology Officer of IMVU. He serves on the advisory board of a number of technology startups, and has worked as a consultant to a number of startups, companies, and venture capital firms. Case Study: Continuous deployment makes releases n. I will come back for more.

San Francisco 155

San Francisco Technical Cofounder Fractional CTO CTO 155

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

San Francisco 119

San Francisco Management Continuous Deployment Lean 119

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. are there any good substitutes?

San Francisco 128

San Francisco Lean Continuous Deployment DC 128

Startup Lessons Learned

FEBRUARY 9, 2009

and lean manufacturing to guide the creation of technology businesses that create disruptive innovation. ► 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. Expo (and a call for he.

Lean 68

Lean San Francisco Web Advisory Board 68

Startup Lessons Learned

SEPTEMBER 22, 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. Case Study: Continuous deployment makes releases n. No departments The Five Whys for Startups (for Harvard Business R.

San Francisco 167

San Francisco CPA SEM CTO Hire 167

Startup Lessons Learned

JANUARY 12, 2010

I continue to believe that the explosion of interest in the lean startup has very little to do with me. Recent economic events, technological change, and the rapid diffusion of information about the old models have combined to help us all realize just how important entrepreneurship is - and just how little we really know about it.

Lean 146

Lean San Francisco Wiki Startup 146

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

Startup Lessons Learned

SEPTEMBER 10, 2008

But if you want to practice rapid deployment, you need to be able to deploy that build in one step as well. If you want to do continuous deployment, youd better be able to certify that build too, which brings us to. For more on continuous deployment, see Just-in-time Scalability. Can you make a build in one step?

Software Review 144

Software Review Technical Review San Francisco Continuous Deployment 144

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). Read the rest.

Lean 68

Lean San Francisco Continuous Deployment DC 68

Startup Lessons Learned

SEPTEMBER 10, 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. Case Study: Continuous deployment makes releases n. No departments The Five Whys for Startups (for Harvard Business R.

Software Review 68

Software Review San Francisco Technical Review Continuous Deployment 68

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. Case Study: Continuous deployment makes releases n. No departments The Five Whys for Startups (for Harvard Business R.

Audience 119

Audience San Francisco Continuous Deployment Lean 119

Startup Lessons Learned

SEPTEMBER 2, 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. Case Study: Continuous deployment makes releases n. No departments The Five Whys for Startups (for Harvard Business R.

San Francisco 142

San Francisco Continuous Deployment Lean DC 142

Startup Lessons Learned

NOVEMBER 4, 2008

As Ive written previously , lean startups are built upon three main trends: Technology commoditization. Combined with the technology trends above, it also enables rapid deployment strategies like just-in-time scalability. Case Study: Continuous deployment makes releases n. Agile software development.

Lean 102

Lean San Francisco Agile Continuous Deployment 102

Startup Lessons Learned

MAY 27, 2009

Lessons Learned by Eric Ries Wednesday, May 27, 2009 Austin: the Lean Startup tour continues Next week I head to Austin, TX for my first visit ever. and lean manufacturing to guide the creation of technology businesses that create disruptive innovation. Case Study: Continuous deployment makes releases n. Learn more here.

Lean 60

Lean Austin San Francisco Continuous Deployment 60

Startup Lessons Learned

SEPTEMBER 2, 2008

After an hour with a team talking dirty about deployment, youll know. ► 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.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

FEBRUARY 22, 2009

That data is completely consonant with the people I know who are successful technologists today, and similar patterns are documented in each recent wave of technology innovation. Case Study: Continuous deployment makes releases n. Its this second point I want to emphasize. Two Ways to Hold Entrepreneurs Accountable (for Ha.

Programming 143

Programming San Francisco Lean Continuous Deployment 143

Startup Lessons Learned

SEPTEMBER 14, 2008

Today, when I talk to startup founders, the most common answer I get to the question "do you talk to your customers?" ► 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.

San Francisco 131

San Francisco Customer Lean Continuous Deployment 131

Startup Lessons Learned

NOVEMBER 17, 2008

Playing with new technologies. Some companies and founders refuse to serve existing customers, and are always lurching from one great idea to the next. Case Study: Continuous deployment makes releases n. Four kinds of work Innovation / R&D - this is what all startups do in their earliest stages. Seeing whats possible.

San Francisco 88

San Francisco Lean Continuous Deployment DC 88

Startup Lessons Learned

JANUARY 19, 2009

I want to talk specifics, and when you come right down to it, most technology startups dont have a very interesting cost structure. Returning to our example of the beleaguered founder who still has the pager, before hiring an operations guy, try promoting someone from within to take on the job. The blog is fantastic as well.

Lean 140

Lean Hiring San Francisco Continuous Deployment 140

Startup Lessons Learned

JANUARY 2, 2009

My son is planning a software product that will take the mystery out of wikis and make the technology easier for consumers to use. Here in Tampa, our biggest challenge is convincing the regions technology "leadership" that grassroots economic development is a good thing. Case Study: Continuous deployment makes releases n.

San Francisco 60

San Francisco Tampa Continuous Deployment Lean 60

Startup Lessons Learned

SEPTEMBER 15, 2008

It was actually my co-founder Will Harvey who taught me to present this data in the simple format weve discussed in this post. ► 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.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166

Startup Lessons Learned

SEPTEMBER 10, 2008

Among his ideas are that todays kids should be taught in class in a way that is relevant to their actual lives, which necessarily means allowing them to use technology. Case Study: Continuous deployment makes releases n. Why ban cell phones when we can take advantage of the fact that, in most classes, they are pervasive.

San Francisco 60

San Francisco Continuous Deployment DC Lean 60

Startup Lessons Learned

SEPTEMBER 1, 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. Case Study: Continuous deployment makes releases n. No departments The Five Whys for Startups (for Harvard Business R.

San Francisco 68

San Francisco Developer Continuous Deployment DC 68

Startup Lessons Learned

SEPTEMBER 10, 2008

Too often, startup founders talk about how they are pushing to get to “critical mass&# and how “economies of scale&# are going to kick in. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

San Francisco 76

San Francisco Continuous Deployment Lean DC 76

Startup Lessons Learned

JUNE 17, 2010

They are leaders, visionaries, founders and managers having tremendous success. The engineering team feels burned too, and feels that they were blamed for deficiencies in the spec as if it was their fault that the technology doesn’t really support what the artists want to do. Case Study: Continuous deployment makes releases n.

Technical Review 164

Technical Review San Francisco Lean Software Review 164

Startup Lessons Learned

SEPTEMBER 2, 2008

We talk a good game about technology adoption curves and crossing the chasm, but most of us dont seem to recognize when its happening. ► 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.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

SEPTEMBER 16, 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. Case Study: Continuous deployment makes releases n. No departments The Five Whys for Startups (for Harvard Business R.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

SEPTEMBER 6, 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. Case Study: Continuous deployment makes releases n. No departments The Five Whys for Startups (for Harvard Business R.

San Francisco 60

San Francisco Continuous Deployment Lean DC 60

Startup Lessons Learned

AUGUST 24, 2009

The other revels in the world as we all know it will be someday: limitless distribution enabled by new technologies, the importance of collaborative filters, and on-demand availability of all content for end-users. But the same technologies that make life difficult for traditional marketers also offer them unprecedented new opportunities.

San Francisco 113

San Francisco Lean Technical Review Distribution 113

Startup Lessons Learned

JULY 29, 2009

To do that, we add specific speed regulators, like integrating source control with our continuous integration server or the more elaborate dance required for continuous deployment. Case Study: Continuous deployment makes releases n. One last thought. He’s right. path hence urgently pushing to release asap.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

SEPTEMBER 18, 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. Case Study: Continuous deployment makes releases n. No departments The Five Whys for Startups (for Harvard Business R.

San Francisco 133

San Francisco Lean Continuous Deployment DC 133

Startup Lessons Learned

OCTOBER 20, 2008

Today, the transformations are often from migrating all those rudimentary legacy systems into a technological windtunnel described by Ray Kurzweil in The Singularity is Near. I'm sure we all agree the technology landscape has changed in the last 30 years, but are you blaming agile development for the global financial crisis?

Software Review 164

Software Review Engineer Management Technical Review 164

Startup Lessons Learned

SEPTEMBER 3, 2009

If you look at the typical startup, you will see the vast majority of their energy and time invested in building new technology. We act as if the biggest risk to startup success is that the technology won’t work. Case Study: Continuous deployment makes releases n. Take the example of the Hoverboard.

San Francisco 104

San Francisco DC Continuous Deployment Lean 104