Continuous Deployment, Demand, Design and Software

Why Continuous Deployment?

Startup Lessons Learned

JUNE 15, 2009

Lessons Learned by Eric Ries Monday, June 15, 2009 Why Continuous Deployment? Of all the tactics I have advocated as part of the lean startup , none has provoked as many extreme reactions as continuous deployment , a process that allows companies to release software in minutes instead of days, weeks, or months.

Continuous Deployment

Continuous Deployment Software Review San Francisco Lean

Lessons Learned: Continuous deployment and continuous learning

Startup Lessons Learned

FEBRUARY 10, 2009

Lessons Learned by Eric Ries Tuesday, February 10, 2009 Continuous deployment and continuous learning At long last, some of the actual implementers of the advanced systems we built at IMVU for rapid deployment and rapid response are starting to write about it. At IMVU it’s a core part of our culture to ship.

Continuous Deployment

Continuous Deployment San Francisco Software Review Lean

Beyond the garage

Startup Lessons Learned

APRIL 25, 2011

It may be hard to remember that there was a time when people in the agile software development community thought Lean Startup was incompatible with agile practices. Brad Smith is the CEO of Intuit, one of the most successful software companies in Silicon Valley. Design + Lean Startup = Lean UX. We’re just getting started.

San Francisco

San Francisco Silicon Valley Lean Agile

Minimum Viable Product: a guide

Startup Lessons Learned

AUGUST 3, 2009

My experience is in Enterprise Software - where we are forced to chunk features into formal releases. Iterate quickly to uncover true market demands. Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ▼ 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

San Francisco

San Francisco Product Lean Continuous Deployment

Lessons Learned: Stevey's Blog Rants: Good Agile, Bad Agile

Startup Lessons Learned

NOVEMBER 6, 2008

Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective. They take things like unit testing, design documents and code reviews more seriously than any other company Ive even heard about. Case Study: Continuous deployment makes releases n.

Agile

Agile San Francisco Software Review Continuous Deployment

Lessons Learned: About the author

Startup Lessons Learned

OCTOBER 4, 2008

Although Catalyst folded with the dot-com crash, Ries continued his entrepreneurial career as a Senior Software Engineer at There.com, leading efforts in agile software development and user-generated content. I know many people who think that software works like magic, but to me it actually was magic.

San Francisco

San Francisco Technical Cofounder Fractional CTO CTO

Lessons Learned: Five Whys

Startup Lessons Learned

NOVEMBER 13, 2008

Best of luck, Your Software." (OK, I picked up on the 5 whys from Joel on Software earlier this year. It seems your cluster architecture is one of the key architectural constraints making continuous deployment possible. Case Study: Continuous deployment makes releases n. OK, thats not exactly what it said.

Software Review

Software Review Technical Review San Francisco Continuous Deployment

Lessons Learned: What does a startup CTO actually do?

Startup Lessons Learned

SEPTEMBER 30, 2008

It became harder and harder to separate how the software is built from how the software is structured. If youre trying to design an architecture to maximize agility, how can that work if some people are working in TDD and others not? If not, whos going to insist we switch to free and open source software? I dont think so.

CTO

CTO Fractional CTO CTO Hire Technical Review

Embrace technical debt

Startup Lessons Learned

JULY 29, 2009

Like a financial debt, the technical debt incurs interest payments, which come in the form of the extra effort that we have to do in future development because of the quick and dirty design choice. We can choose to continue paying the interest, or we can pay down the principal by refactoring the quick and dirty design into the better design.

Technical Review

Technical Review Software Review San Francisco Lean

Good enough never is (or is it?)

Startup Lessons Learned

SEPTEMBER 27, 2010

This is precisely the dilemma that the doctrine of minimum viable product is designed to solve. When people start using quality, reliability, or design as an excuse to delay, it used to make me nervous, even when these suggestions were well intentioned. Rules of thumb can be infuriatingly unhelpful. And it’s really hard.

San Francisco

San Francisco Lean Continuous Deployment Software Review

Lessons Learned: Principles of Lean Startups, presentation for.

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

Lean San Francisco Agile Continuous Deployment

Lessons Learned: What is customer development?

Startup Lessons Learned

NOVEMBER 8, 2008

For software, we have many - you can enjoy a nice long list on Wikipedia. This is a self-published book, originally designed as a companion to Steves class at Berkeleys Haas school of business. Case Study: Continuous deployment makes releases n. Using AdWords to assess demand for your new online. Heres the catch.

Customer Development

Customer Development Developer San Francisco Customer

Lessons Learned: Product development leverage

Startup Lessons Learned

APRIL 26, 2009

We combined three tactics: extensive use of free software, an open platform for user-generated content, and leveraged distribution channels. In that same spirit, here are some suggestions for tactics you can use to increase the leverage of your product development efforts: Free and open source software (and even hardware ).

Product Development

Product Development Developer San Francisco Product

Lessons Learned: The hacker's lament

Startup Lessons Learned

DECEMBER 7, 2008

As the company grows, hes the go-to person for almost everything technical, and so hes very much in demand. 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. But life is not easy, either.

Software Review

Software Review Technical Review Part-Time VPE San Francisco

How to conduct a Five Whys root cause analysis

Startup Lessons Learned

JULY 2, 2009

Five Whys is designed to avoid these nebulous arguments. Furthermore, I think most of what you are suggesting is applicable in companies/ industries that are not software development. oh, and on the book front, you'll be able to get all of my essays so far in ebook, print-on-demand, and kindle editions - coming soon.

San Francisco

San Francisco Lean Technical Review Software Review

Lessons Learned: The ABCDEF's of conducting a technical interview

Startup Lessons Learned

NOVEMBER 29, 2008

For software engineers, I think this absolutely has to be a programming problem solved on a whiteboard. Its nearly impossible to get a good read on all six attributes in a single interview, so its important to design an interview process that will give you a good sampling of data to look at. Does their personality bring something new?

San Francisco

San Francisco Lean Agile Java

Marching through quicksand

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. Case Study: Continuous deployment makes releases n. Revisiting the Software Design Manifesto (and what.

San Francisco

San Francisco Lean Technical Review Distribution

Learning from Obama: maneuver warfare on the campaign trail

Startup Lessons Learned

NOVEMBER 5, 2008

Wed train them on-demand as they came in, and send them into the world (or onto the phones) with written instructions and voter contact data. Our campaigns software tools were pretty poor (dont let the fancy website fool you, the volunteers are working from an antiquated system). Case Study: Continuous deployment makes releases n.

Campaign

Campaign San Francisco Lean Agile

Lessons Learned: What is a market? (a guide for hackers)

Startup Lessons Learned

FEBRUARY 12, 2009

(a guide for hackers) (This post was inspired by a conversation with Nivi from Venture Hacks , but is otherwise not his fault) There has been a proliferation of frameworks and metaphors lately that are designed to help startups avoid the all-too-common fatal mistake of failing to find a market. Tough sell. Expo (and a call for he.

San Francisco

San Francisco Continuous Deployment Ruby Lean

Lo, my 1032 subscribers, who are you?

Startup Lessons Learned

NOVEMBER 19, 2008

What all these teachers had in common were two things: they were technology early adopters that were willing to take a chance on a new software product, and they all had similar problems organizing their classes and students. Case Study: Continuous deployment makes releases n. Using AdWords to assess demand for your new online.

San Francisco

San Francisco Lean Continuous Deployment DC

Lessons Learned: Where did Silicon Valley come from?

Startup Lessons Learned

NOVEMBER 11, 2008

Just to pick one: will software patents, NDAs and trade secrets laws make it harder for people to share knowledge outside of big companies? Case Study: Continuous deployment makes releases n. Towards a new entrepreneurship ► 2009 (88) ► December (4) Continuous deployment for mission-critical applica.

Silicon Valley

Silicon Valley San Francisco Lean Continuous Deployment

The cardinal sin of community management

Startup Lessons Learned

SEPTEMBER 11, 2009

or their privileging of only certain designers featured in Showcase and promos. until I couldn't seem to find a way from getting away from all these nasty, vulgar teens (or people pretending to be teens) demanding explicit sex every time I went there. Case Study: Continuous deployment makes releases n. So I gave up.

Community

Community Management Lean Software Review

StartUpRoar

Why Continuous Deployment?

Lessons Learned: Continuous deployment and continuous learning

Trending Sources

Beyond the garage

Minimum Viable Product: a guide

Lessons Learned: Stevey's Blog Rants: Good Agile, Bad Agile

Lessons Learned: About the author

Lessons Learned: Five Whys

Lessons Learned: What does a startup CTO actually do?

Embrace technical debt

Good enough never is (or is it?)

Lessons Learned: Principles of Lean Startups, presentation for.

Lessons Learned: What is customer development?

Lessons Learned: Product development leverage

Lessons Learned: The hacker's lament

How to conduct a Five Whys root cause analysis

Lessons Learned: The ABCDEF's of conducting a technical interview

Marching through quicksand

Learning from Obama: maneuver warfare on the campaign trail

Lessons Learned: What is a market? (a guide for hackers)

Lo, my 1032 subscribers, who are you?

Lessons Learned: Where did Silicon Valley come from?

The cardinal sin of community management

Stay Connected