i need to write a scope of work can you help.

Here is a nice Scope document sample.  It also gives the reasons why a good, detailed scope document is necessary:  http://articles.techrepublic.com.com/5100-10878_11-1044366.html

Here is a sample "template" for a scope document: http://www.google.com/url?sa=t&source=web&ct=res&cd=4&url=http%3A%2F%2Fwww.harborlightmanagement.com%2FPublications%2FScope%2520Document.pdf&ei=sGt0SoyOIdiptgef-tGWCQ&rct=j&q=scope+document+sample&usg=AFQjCNH4crmh864yV3smD60tewUF5H0SNg&sig2=Oeb-wdm2MZCf_XdhxgswvQ

besmile4ever:

In addition to and clarifying some of the items in the prior posts, pay particular attention to and document the following:

1) Specify all goals and requirements in absolute terms.  ie:  "The system will process 1,000 transactions per hour" as opposed to "The system will have a high throughput."

2) In the Risks section, spell out the mitigation strategy or strategies, for each risk.

3) Spell out any work that is "out of scope" that someone might assume is "in scope."  For example, a user may assume that a full suite of reports is included based on the heavy data entry use of the system.  If reports are in another project or budget, specifically list them as "excluded" or "not in scope."

Cover yourself and project team by including language like "Any feature not explicitly mentioned in this document is not in scope."

4) List any dependencies on scheduled events.  If the client is to provide a server by the first of the month, and you are to have software installed by the 15th of the month, note that for each day there is a delay in the delivery of the server, there will be a one business day delay in the software installation and all related tasks.

5) List the sign off criteria in the scope document, such as: "The client shall sign off on the project when the software is capable of running 4 hours of production processing without aborts or errors for 4 consecutive business days.

6) You can cover this in the Conceptual Solution section, but I usually include a section called Approach, which outlines the system overview.  List what resources that already exists in the company that will be leveraged, and what will need to be purchased.  ie:  The project will be hosted on the existing web server (Maximus1) enhanced with an Oracle v10.i database.  The system RAM will be upgraded to 4Gb, and the all operating system service patches applied."

7) Add a section at the bottom of the document for the names, responsibilities, and signatures, of all stakeholders and management from both the client and the development team / company.

In general, be explicit, and things should go smoothly.  A good Scope and Approach document is an interface between the business and the development team.  It protects both sides by explaining to the business what they are, and ARE NOT, getting; and the development team by explicitly stating what requirements must be delivered, and what the sign off (usually payment) criteria are.

Best of luck,

AielloJ