agile.brazism
What killed us was “one more thing.” We could have easily done three major releases that year if we had drawn a line in the sand, said “finished,” and shipped the darn thing. The problem is that the longer it’s been since your last release the more pressure and anticipation there is, so you’re more likely to try to slip in just one more thing or a fix that will make a feature really shine. For some projects, this literally goes on forever.

-

1.0 Is the Loneliest Number — Matt Mullenweg

Good article about the need to actually ship - “Great artists ship” - that’s summed up in one sentence:

But if you’re not embarrassed when you ship your first version you waited too long.

Getting your product out the door, in front of users, is still the best way to find out what they actually want and need, instead of studies and surveys and interviews. Get people to use it, get them to complain about it, and that single act will provide you with all the information you need to prioritize the “What’s Next” list of features for 1.1, 2.0, 3.0 and beyond.

Ship it. Get it out the door.

About

talkin' the talk, with the battle scars to back it up

Ask me anything

Search

Following