• Advertisement

Archived

This topic is now archived and is closed to further replies.

Just curious: How do you determine when a project is "done"?

This topic is 5285 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

We all know that nothing is ever really finished when it comes to programming. I was just wondering if anyone has any specific criteria they use to determine if a project is ready for release.

Share this post


Link to post
Share on other sites
Advertisement
Well, where I work a release is "done" when everyone involved in the project signs off on it. That normally includes developers, quality assurance, documentation, and managers. Of course for indie development, you''ll probably be a little less formal. But I''d suggest keeping some idea of a version of your product needing to meet certain functional and stability requirements before you consider it done and move on to the next version/project.

Share this post


Link to post
Share on other sites
It is considered done at the exact second before your final deadline in which the people paying the bills say it has to be done. If no is paying the bills, then it is never done.

Share this post


Link to post
Share on other sites
In general terms, you can say your project is done when it accomplish (more or less flawlessly) all the objectives you wanted it to accomplish before you started coding it.

[edited by - owl on September 3, 2003 3:14:22 PM]

Share this post


Link to post
Share on other sites
For an indie project, it is done when you absolutely can not stand to even load the damn thing up in your IDE anymore, much less actually execute and play the SOB. When you feel nausea at the sight of the opening screen, call it finished and move on.

Josh
vertexnormal AT linuxmail DOT org


Check out Golem at:
My cheapass website

Share this post


Link to post
Share on other sites
I never have the feeling that a project is really done, only the feeling that a project is "ready to be published".

Share this post


Link to post
Share on other sites
Your own project is done when any more changes you can think of would mire its original expression.

Share this post


Link to post
Share on other sites
Not literally speaking, it should be done before you ever start on it, like on paper.

Share this post


Link to post
Share on other sites
quote:
Original post by smitty1276
We all know that nothing is ever really finished when it comes to programming.

I disagree. I have programs that are done and really finished. The most recent one was for my sister. It was a small alert/note program. It is truely finished because it has everything she wanted. I see no reason for considering it "unfinished"


Colin Jeanne | Invader''s Realm

Share this post


Link to post
Share on other sites
A program is not done until it can play all your audio and video, and send/receive e-mail.

Share this post


Link to post
Share on other sites
quote:
Original post by Magmai Kai Holmlor
When you''re paid-in-full for it.


Yeah!!! :D Thát''s when it''s done!!!
ROFLOLMAO

Share this post


Link to post
Share on other sites
When the customer stops whining about missing features he never asked for, and begins grumbling about bugs that are really features

[edited by - LNK2001 on September 5, 2003 12:57:00 PM]

Share this post


Link to post
Share on other sites

  • Advertisement