Estimating Project Scope

| Total Words: 624

Whenever I am beginning a new software development project the clients first questions are: what is it going to take? and how much is it going to cost?. These are two very big questions and normally take a lot of system analysis work to derive. This can be done in various ways and everyone has there own preference. I normally put together a project scope document that lays out many of the fundamental parts of the development effort.

So far my largest project scope document has been 14 pages, but I have also done small ones that fit nicely into emails. The length of the document is largely dependant on the size and complexity of the system you are implementing. It usually takes anywhere from 3 hours to 2 days to gather the required information and I dont charge anything for the analysis. This is kind of like requirements gather, but not as detailed. I usually jot down a few key requirements that will largely impact the scope.

When doing this analysis you need to gather what kind of architecture would best fit the company. If the company has plans for rapid growth an Object Oriented or Service Orient Architecture would probably fit best. Also gather as many...

To view and download this full PLR article, you must be logged in. Registration is completely free. Once you create your account, you will be able to browse, search & downlod from our PLR articles database of over "1,57,897+" on 1,000's of niches and 200+ categories without paying a penny. Click here to signup...

** PLR to VIDEO: Create Awesome Videos From PLR Articles... FAST!...