Agile Development Quotes

I've long believed that if you're not embarrassed by your first product release, you've released too late.

Developers, developers, developers, developers.

Because startups often accidentally build something nobody wants, it doesn’t matter much if they do it on time and on budget. The goal of a startup is to figure out the right thing to build - the thing customers want and will pay for - as quickly as possible.

If you are not embarrassed by the first version of your product, you've launched too late.

But typically for a project like the Mac, the size we had was pretty good. And it has different stages. The team grows as you have to write manuals and do testing... though the Mac had no formal testing.

I would say, as an entrepreneur everything you do - every action you take in product development, in marketing, every conversation you have, everything you do - is an experiment. If you can conceptualize your work not as building features, not as launching campaigns, but as running experiments, you can get radically more done with less effort.

The community of developers whose work you see on the Web, who probably don't know what ADO or UML or JPA even stand for, deploy better systems at less cost in less time at lower risk than we see in the Enterprise. This is true even when you factor in the greater flexibility and velocity of startups.

I take a lean-startup approach: creating agile, interdisciplinary teams that get the minimum viable product to market as soon as possible. It's my job to be entrepreneur-in-residence, an internal change agent.

The Waterfall Model is wrong and harmful; we must outgrow it.

In a start-up company, you basically throw out all assumptions every three weeks.

If you're not embarrassed when you ship your first version, you waited too long.

Get your product into users' hands as quickly as possible and incorporate the crowd's feedback to iterate. Your customers will provide the data you need to chart the best course for your company and bury any competitor that goes it alone.

Revolutionary products don't fail because they are shipped too early. They fail because they aren't revised fast enough.

Decades before we were able to articulate the value of 'getting out of the building' and the Lean Startup, the value in having skunk works controlling their own distribution was starkly evident.

Essentials of how to do a startup do not include writing a business plan

Responsible Development shares many practices with XP but the roots are different. Responsible Development's values are honesty, transparency, accountability and responsibility. These lead me to pairing, test-first, incremental design, continuous integration and so on because they support the values.

The Googly thing is to launch products early on Google Labs and then iterate, learning what the market wants - and making it great. The beauty of experimenting in this way is that you never get too far from what the market wants. The market pulls you back.

The best founders work on things that seem small but they move really quickly. They get things done really quickly.

Right now, nearly all the apps on Facebook take a week to build. No more.

Make mistakes faster.

Be big, fast and flexible.

Don't spend too much time planning, release early and often, some things will work, others won't, refine and move forward and above all forget the money, just make sure you love what you're doing.

People think innovation is just having a good idea but a lot of it is just moving quickly and trying a lot of things.

We used to write this down by saying, 'move fast and break things.' And the idea was, unless you are breaking some stuff you are not moving fast enough. I think there's probably something in that for other entrepreneurs to learn which is that making mistakes is okay. At the end of the day, the goal of building something is to build something, not to not make mistakes.

Developers, developers, developers...