Your Most Successful Project

Had a funny conversation with a colleague the other day where we talked about coding, project process, platform, etc. and we started talking about "Our Most Successful Project" and what it was and why. Interesting where it took us...

What Was Your Most Successful Project?
The first question that comes to mind, of course, is "what do you call success?" and it's a reasonable one. It's also not easily answered - what are your metrics? Are they:

• Money - did you make some? A lot? Does this mean you wrote good software?
• Time - did it come together like butta and sing its way to the finish line?
• Completeness - did you nail every requirement? Was it bug free with 100% code-coverage?
• Client-happiness - did your client get a promotion? Gush about you and your company?

Perhaps it's a mix of all four. And then again perhaps it's none of these - maybe it's just a "gut feeling" you have that you "nailed it".

I think about these things a lot - especially since I'm putting my bits on the block with the MVC Storefront and it better be good. But WTF is *good* anyway? Will it be *good* if the Alt.NET guys talk to me still? Is it *good* if Ayende says it is?

What if I can go to bed at night and feel like I didn't sell my soul to the Great Soul-Sucker, and people use it?

Meh. You can freak yourself out on this to no end. So rather than look forward and worry - I think it's better to look backward and reflect and ask yourself - What Was the Most Successful Project You Worked On?

Note that i'm not asking about code here - I'm asking about the SUCCESS of the project. Qualify it as you will - based on code, technology, client happiness, money - preferably a sweet mix of all 4!

I had a moment to think about this tonight as I pulled my kids around the block in their Red Wagon - what was MY most "successful" project? I'd say it has to be SubSonic.

My Most Successful Project
People use it, they like it, and it seems to be very useful - which is what I intended. This isn't supposed to be an ego-stroke post, but it's something I want to look back on so I can see what's important as I push ahead with other projects.

SubSonic isn't technically marvelous and exciting, by any stretch. The docs completely suck, the support is not where it should be (though I really, really try), and our test coverage is ... well I spose I shouldn't even use that word with respect to our unit tests :).

I didn't use BDD or TDD, I didn't follow BDUF or make Eric join me in weekly scrums. I didn't do any kind of focus group or marketing either - I just had an idea and it lit me up.

So I spose what I'm saying is that it was accidental :). It was inspired - to be sure, but really it was (as they always say) a matter of right place, right time, and right idea and I made something that people found useful.

Which is market-speak and has nothing to do with technical approaches or project processes. To be honest I'm OK with that - I'm working on 3.0 right now and so far have implemented what I think are pretty decent approaches (like I did with 1.0 2 years ago, and I'm sure I'll do again with 4.0 two years from now). The point I can't get away from is that, technically speaking, it's more about the itch that SubSonic scratches than the fluffy stuff that makes it up.

There's a messaging service out there that shows cats in servers and whales supported by birds (James and the Giant Fail Whale) but I'll be damned if I try to make a comparison there... not good...

I'm interested to hear what you have to say about this - how do you gauge the success of something you've worked on or created?