Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister

Re: Re: Starting a Large Project

by mattriff (Chaplain)
on Feb 12, 2002 at 02:45 UTC ( #144767=note: print w/replies, xml ) Need Help??

in reply to Re: Starting a Large Project
in thread Starting a Large Project

For me, the most important step in any large project is putting together a good 'specifications' or 'requirements' document. If you can do this in enough detail, and have the client sign off on it, you can save yourself a lot of work.
I'd like to second, third, and fourth that. :)

I've worked on several projects that skimped early on in the requirements gathering phase, and we suffered for it later. All I can say is, I'll never let that happen to me again.

Designing a beautiful architecture only to find that it can't be made to meet the end-user's needs is no fun. Making up the requirements as you go along is fun for a few months, but then it starts to get old.

As much as you can, it's good to know where you need to end up before you get started.


Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://144767]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others making s'mores by the fire in the courtyard of the Monastery: (5)
As of 2019-06-20 21:10 GMT
Find Nodes?
    Voting Booth?
    Is there a future for codeless software?

    Results (91 votes). Check out past polls.