Project Scope Document

ProjectDocument Project Scope Document—that is, the defin" rel="nofollow">inition of what needs to be done to produce the project deliverables and to satisfy the customer. The project scope document should satisfy the followin" rel="nofollow">ing components: 1. Customer Requirements a. Defin" rel="nofollow">ines the functional or performance specifications of the project’s end product 2. Statement of Work (SOW) a. Defin" rel="nofollow">ines the major tasks or work elements to be performed to accomplish and produce all project deliverables 3. Deliverables a. Products to be accomplished for duration of and conclusion of the project 4. Acceptance Criteria a. Must be described in" rel="nofollow">in greater detail than what is stated in" rel="nofollow">in the project proposal 5. Work Breakdown Structure a. A hierarchical breakdown of the scope in" rel="nofollow">into smaller work packages that produce the deliverables The above components are only brief descriptions. While project scope documents may vary from project to project, your document should contain" rel="nofollow">in a thorough description of each section. If your project varies in" rel="nofollow">in such a way that a thorough description is not possible, you will then in" rel="nofollow">include elements of the section in" rel="nofollow">in question to at least provide an outlin" rel="nofollow">ine of what is provided. Your project scope document should be a min" rel="nofollow">inimum of three pages in" rel="nofollow">in length. Use APA style writin" rel="nofollow">ing and citations when you craft your proposal. Also, make sure you use Times New Roman, 12 font, double spaced.