instructions:

1.write a project name.

2 Scope Description

The next block you'll see in the project scope statement document is the scope description, but you should actually complete this section last, once you're confident you have a holistic understanding of the project.

Skip over this section for now and move to the objectives section.

3) Objectives

The objectives section should outline the measurable end result that determines what your project will accomplish within the given time frame. Remember that the objective should be SMART. An objective is mentioned in the project charter, but see if you can improve it.

Navigate to the project scope statement document, then fill in the section below the "Objectives" heading.

4) Deliverables

The deliverables section should include all products, outcomes, services, and measurable results produced by your project's completion.

Navigate to the project scope statement document, then fill in the section below the "Deliverables" heading. In this instance, you can copy word-for-word the deliverables outlined in the project charter.

5) Acceptance Criteria

Your acceptance criteria should include all conditions your deliverables must meet in order to be approved. Acceptance criteria are specific and focus heavily on required features and product characteristics.

Navigate to the project scope statement document, then fill in the section below the "Acceptance Criteria" heading, using the appropriate information from your project charter.

6) Constraints

The constraints section should include all of the limiting factors that apply to a project and its workflows. Constraints can encompass project timelines, costs, scope, resources, and more.

In order to complete the constraints section, you need more information than you can find in the project charter. You email Simone, the project sponsor, to ask the following questions:

What are the time and budgetary constraints for this project?

What are the human resource constraints on this project?

Are there any other constraints that I should be aware of?

Simone calls you and leaves you the following voice message with information about constraints. Listen to the voice message below. (You should probably take notes as you listen.) You can find a full transcript of the call at the bottom of this page under "Links to Text Versions of Documents."

Constraints

Navigate to the project scope statement document, then fill in the section below the "Constraints" heading using the appropriate information from this voice message.

7) Assumptions

The assumptions section should include all of your known assumptions surrounding the resources to which you will have access, as well as the objectives you will work toward for the project's duration.

In order to complete the assumptions section, you need more information than you have in the project charter. You follow up again with Simone, the project sponsor and ask the following question:

What are the assumptions we are making for this project?

Now, navigate to the project scope statement document, then fill in the section below the "Assumptions" heading using the appropriate information.

8) Exclusions

The exclusions section details all work that will not be in scope for the project's duration. Outlining specifically what work is excluded helps the project team focus their energy solely on work that is in scope. Outlining what will be excluded early on also helps to set project expectations for all stakeholders.

Navigate to the project scope statement document, then fill in the section below the "Exclusions" heading, using the appropriate information from your project charter.

9) Scope Description

It's finally time to complete the scope description section.

Within the scope description, you should include a thorough but succinct summary of the project scope (what is in and out of scope) and the product scope (what deliverables or results will be produced). You should also include any project exclusions.

Your project scope should include the work performed to deliver the project's product, service, or result, while the product scope should highlight the features that characterize the product, service, or result.

Navigate to the project scope statement document, then fill in the section below the "Scope Description" heading with a short paragraph, using the appropriate information from your project charter.

6) Assumptions

The assumptions section should include all of your known assumptions surrounding the resources to which you will have access, as well as the objectives you will work toward for the project's duration.

In order to complete the assumptions section, you need more information than you have in the project charter. You follow up again with Simone, the project sponsor and ask the following question:

What are the assumptions we are making for this project?

Listen to the voice message Simone leaves you about assumptions and take notes on the assumptions.

7) Exclusions

The exclusions section details all work that will not be in scope for the project's duration. Outlining specifically what work is excluded helps the project team focus their energy solely on work that is in scope. Outlining what will be excluded early on also helps to set project expectations for all stakeholders.

Navigate to the project scope statement document, then fill in the section below the "Exclusions" heading, using the appropriate information from your project charter.

8) Scope Description

It's finally time to complete the scope description section.

Within the scope description, you should include a thorough but succinct summary of the project scope (what is in and out of scope) and the product scope (what deliverables or results will be produced). You should also include any project exclusions.

Your project scope should include the work performed to deliver the project's product, service, or result, while the product scope should highlight the features that characterize the product, service, or result.