Project Scope Statement

Project Scope Statement

Scope Statement Essential Components

Connect with a professional writer in 5 simple steps

Please provide as many details about your writing struggle as possible

Academic level of your paper

Type of Paper

When is it due?

How many pages is this assigment?

For this assignment, you will develop a scope statement that will be used to define the project requirements and exclusions. The scope statement should include the following elements:

· Executive Summary – 2-3 paragraph summary of the business needs and key features of the project.

· Business Requirements – The specific statement(s) that describe the business problem to be solved.

· Solution Requirements – A list of all relevant technical, project and regulatory requirements that effectively solve the project’s business objectives. Solution requirements must be classified by priority.

· Exclusions (Out of Scope) – Items that will not be addressed by the project.

· Key Project Features – In this section, identify any conditions that limit project planning. Constraints of the project such as “must have “milestones, constrained due dates, events or budgetary restrictions.

· Assumptions & Risks – Identified risks and/or assumptions from the business case and project charter.

· Approvals – Space for key stakeholders to formally review approve all sections of the scope statement content. (Note: Best practice is that the Project Sponsor reviews and approves key project management documents).

Textbook: Project Management: The Managerial Process (attached)

Assignment

Create a Project Scope Statement

Overview and Rationale

One of the initial stages of planning a project is to create a project scope statement that guides the development of the project work. In this assignment you will create a project scope statement for your chosen project.

Program and Course Outcomes

The following course learning objectives are addressed through this assignment:

· Know tools and techniques used to effectively define a project’s scope

· Describe common components of an effective project scope statement

· Build a project scope statement

 

Scope Statement Essential Components

For this assignment, you will develop a scope statement that will be used to define the project requirements and exclusions. The scope statement should include the following elements:

· Executive Summary – 2-3 paragraph summary of the business needs and key features of the project.

· Business Requirements – The specific statement(s) that describe the business problem to be solved.

· Solution Requirements – A list of all relevant technical, project and regulatory requirements that effectively solve the project’s business objectives. Solution requirements must be classified by priority.

· Exclusions (Out of Scope) – Items that will not be addressed by the project.

· Key Project Features – In this section, identify any conditions that limit project planning. Constraints of the project such as “must have “milestones, constrained due dates, events or budgetary restrictions.

· Assumptions & Risks – Identified risks and/or assumptions from the business case and project charter.

· Approvals – Space for key stakeholders to formally review approve all sections of the scope statement content. (Note: Best practice is that the Project Sponsor reviews and approves key project management documents).

The assignment should use business style writing. Do not assume the audience has read the project case.

Assignment Format

Below are some key guidelines you will want to ensure you follow in creating this assignment. Think of this short list as a quality control checklist, along with the attached grading rubric.

· Project Scope Statement template must be complete, please submit in Ms Word (.doc, .docx) or .pdf format

· Format the document professionally:

· Double line spacing between paragraphs but 1.5 spacing within the paragraph

· 12-point Times Roman

· 1-inch margins

· Use footnotes or endnotes and citations

· 2-14-point font, bold headings and subheadings

· Adhere to APA 6th edition conventions

· Please ensure you remove all instructions (italicized) and any examples provided within the template that begins on the next page

Please be sure to review the attached rubric that follows the scope statement template provided. Along with these assignment instructions, the rubric will ensure you have a solid understanding of the assignment requirements and how the assignment will be graded.

 

 

 

 

 

Grading Rubric

Category Above Standard Meets Standards Approaching Standards Below Standard Not Evident
Executive Summary

(10%)

Goes beyond the requirements of the assignment to provide a coherent summary of key points of the Scope Statement Provides a clear and concise summary of key points of the Scope Statement Provides a summary of key points of the Scope Statement, but does not address all areas, is not clear or is not concise Provides a summary of key points of the Scope Statement but is vague and does not introduce the Scope Statement in a sufficient manner Does not provide a summary of key points of the Scope Statement. Information provided is incomplete and insufficient
Requirements (Business and Solution)

(40%)

Provides at least 6 well written and SMART requirements.

Goes beyond the requirements of the assignment to identify and provide analysis of the business problem to be solved and the technical and regulatory requirements for the solution in a coherent and integrated way

Provides at least 6 mostly well written and SMART requirements.

Identifies and provides useful and relevant analysis of the business problem to be solved and the technical and regulatory requirements for the solution. Classifies the solution requirements by priority.

Provides at least 6 requirements. Not all are adequately written (following SMART) guidelines.

Identifies and states the business problem to be solved and the technical and regulatory requirements for the solution, but the problem is not clearly defined or the solution requirements do not address the needs stated. Attempts to classify the solution requirements by priority.

Does not provide at least 6 requirements. Not all are adequately written (following SMART) guidelines.

Identifies and states the business problem to be solved and the technical and regulatory requirements for the solution, but statements are incomplete or the problem and solution do not match. Does not classify the solution requirements by priority.

Does not identify nor provide statements of the business problem or technical and regulatory solutions.
Exclusions and Key Project Features

(15%)

Goes beyond the requirements of the assignment to identify items that will not be addressed by the project and defines milestones, dates, events and budgets in a coherent and integrated way. Explicitly identifies specific items that will not be addressed by the project and clearly defines milestones, dates, events and budgets that assist in scheduling and budgeting activities Identifies items that will not be addressed by the project and defines milestones, dates, events, but exclusions are incomplete or the milestones, dates, event or budgetary restrictions are not defined well enough to assist in scheduling and budgeting activities. Identifies items that will not be addressed by the project and defines milestones, dates, events but the exclusions are generic and vague and key product features are unhelpful Does not identify exclusions. Does not define key product features.
Assumptions and Risk and Approvals

(15%)

Goes beyond the requirements of the assignment to addresses all risk from the project charter, business case and requirements collection process in a seamless and integrated way. Provides space for stakeholder approval Addresses risks identified in the business case and project charter. Updates the risks based on the requirements collection process. Provides space for stakeholder approval Addresses risks from the business case and project charter, but does not fully update risks based on requirements collection process. Provides space for stakeholder approval Addresses risks from the business case and project charter, but does not update risks based on requirements collection process, but does not include all risks from the business case and project charter and does not include any additional risks from the requirements collection process. May or may not provide space for stakeholder approval Does not address risks in the scope statement. Does not provides space for stakeholder approval
Critical Thinking

(15%)

Professional insights into depth and breadth of assignment – goes WELL beyond assignment requirements to explore risks and/or relevant new techniques. Demonstrates comprehensive exploration of issues and ideas before accepting or forming an opinion or conclusion. Demonstrates an exploration of issues and ideas before accepting or forming an opinion or conclusion. Demonstrates exploration of issues and ideas, but shows reluctance to accept or form an opinion or conclusion based on findings. Does not demonstrate exploration of issues and ideas before accepting or forming an opinion or conclusion.
Format & Grammar

(5%)

Goes well beyond assignment requirements to communicate information in a precise, insightful and professional manner. High quality grammar. No misspellings. Scope Statement is well-organized; format can be followed. Evident to reader what is contained in each section (column). High quality grammar. No misspellings. Scope Statement is organized; format can be followed. Evident to reader what is contained in each section (column). Good quality grammar. No misspellings. Scope Statement is reasonably organized, format can be followed. For the most part, evident to reader what is contained in each section (Column). Good quality grammar. Few misspellings. Scope Statement is not presented in an organized format. Not evident to reader what is contained in each section. Low quality grammar, misspellings.