![\"Project](\"https:\/\/plaky.com\/learn\/wp-content\/uploads\/2022\/02\/Project-scope-cover.png\")
<\/figure>\n<\/div>\n\n\n- \n
- Project managers define the scope in agreement with the stakeholders during the project\u2019s planning phase.<\/li>\n\n\n\n
- The scope is usually outlined in a document called the project scope statement of work.<\/li>\n\n\n\n
- A well-written project scope should be specific, measurable, attainable, relevant, and time-based.<\/li>\n\n\n\n
- Stakeholders must approve the final deliverables before the project starts, while project managers have to ensure the project sticks to them.<\/li>\n\n\n\n
- Scope creep happens when stakeholders change the initial goals and deliverables throughout the project.<\/li>\n<\/ul>\n\n\n\n
What is the project scope? <\/h2>\n\n\n\n
The project scope is an agreement between the <\/strong>project team<\/strong><\/a> and the stakeholders that sets the boundaries and expectations from the beginning of the project to its end.<\/strong><\/p>\n\n\n\n
The project scope is determined during the planning phase of the project and includes a clear definition of the project\u2019s:<\/p>\n\n\n\n
- \n
- Goal, <\/li>\n\n\n\n
- Budget, <\/li>\n\n\n\n
- Deliverables, and <\/li>\n\n\n\n
- Due dates.<\/li>\n<\/ul>\n\n\n\n
Experienced project managers<\/a> know how to outline the project precisely so that there\u2019s no misunderstanding during the development or once the final result is delivered. <\/p>\n\n\n\n
In a way, that outline is the first line of defense from additional requests and project failure. So, managers create a detailed document at the beginning of the project\u2019s development.<\/p>\n\n\n\n
What is a project scope statement of work (SOW)?<\/h3>\n\n\n\n
The scope statement of work (SOW) is a document in which project managers define the project scope. <\/strong><\/p>\n\n\n\n
The scope statement defines all the work and criteria needed to complete a project. Therefore, it should include the following:<\/p>\n\n\n\n
- \n
- Justification<\/strong> \u2014 identifies the need for the project, <\/li>\n\n\n\n
- Goals<\/strong> \u2014 identifies what the project aims to achieve,<\/li>\n\n\n\n
- Deliverables<\/strong> \u2014 includes a list and description of everything that the client will receive upon project completion,<\/li>\n\n\n\n
- Limitations<\/strong> \u2014 all rules and guidelines that must be followed while the project is underway, including deadlines and budget constraints,<\/li>\n\n\n\n
- Exceptions<\/strong> \u2014 a list of everything that the project won\u2019t include, and<\/li>\n\n\n\n
- Agreement<\/strong> \u2014 signatures of all key stakeholders as proof that all the involved parties have reviewed, understood, and approved the document.<\/li>\n<\/ul>\n\n\n\n
Everything defined within the scope statement is within scope<\/strong>.<\/p>\n\n\n\n
Everything defined in the \u201cExceptions\u201d section of the document, and everything not defined in the document is considered out of scope<\/strong>.<\/p>\n\n\n\n
A scope statement may include other elements, such as a project timeline<\/a>, key milestones, or a complete list of shareholders \u2014 but the 6 elements mentioned above are necessary to successfully outline the project.<\/p>\n\n\n\n
\n
\n\nOrganize your projects with Plaky<\/h2>\n
Define clear due dates and improve your project planning with Plaky by CAKE.com.<\/p>\n\n
\n Try for free<\/a>\n\n Learn more<\/a>\n <\/div>\n <\/div>\n\n\n\n \n ![\"Illustration\"](\"https:\/\/plaky.com\/learn\/wp-content\/themes\/cake-learn\/src\/images\/plaky\/banners\/default.png\")
\n <\/picture>\n <\/div>\n<\/div>\n <\/p>\n\n\n\nThe importance of defining the project scope<\/h2>\n\n\n\n
The importance of a defined scope may not be visible before the project starts<\/a>, but it makes itself very clear once the team starts working, and the feedback starts coming in.<\/p>\n\n\n\n
A scope statement allows project managers to stay focused only on what\u2019s within the scope. This helps both project managers and other key shareholders stay within the previously defined and agreed boundaries.<\/p>\n\n\n\n
The scope statement is important for project management because it:<\/p>\n\n\n\n
- \n
- Serves as proof of the terms of the agreement, <\/li>\n\n\n\n
- Serves as a reminder of all the project requirements,<\/li>\n\n\n\n
- Protects the team from doing more work than necessary,<\/li>\n\n\n\n
- Prevents the project requirements from spiraling out of control, and<\/li>\n\n\n\n
- Prevents project failure<\/a>.<\/li>\n<\/ul>\n\n\n\n
How to determine and manage the project scope in 6 steps<\/h2>\n\n\n\n
The project scope serves to identify the actions needed to complete the project and ensure that everything goes according to plan during the project execution phase<\/a>.<\/p>\n\n\n\n
There are 6 steps a project manager must perform to properly manage the scope:<\/p>\n\n\n\n
- \n
- Plan scope management, <\/li>\n\n\n\n
- Collect requirements, <\/li>\n\n\n\n
- Define the scope, <\/li>\n\n\n\n
- Create the work breakdown structure (WBS), <\/li>\n\n\n\n
- Validate the scope, and <\/li>\n\n\n\n
- Control the scope. <\/li>\n<\/ul>\n\n\n\n
Let\u2019s get into the details of each step.<\/p>\n\n\n\n
#1 Plan scope management<\/h3>\n\n\n\n
As the first step of scope management, scope management planning serves to create plans for how the next 5 scope management processes will be handled.<\/p>\n\n\n\n
It can be performed either once, at the beginning of the project, or multiple times throughout the project. Its main goals are:<\/p>\n\n\n\n
- \n
- Scope management plan <\/strong>\u2014 a plan that defines how the scope statement and the WBS will be created, as well as how validation will be obtained, and<\/li>\n\n\n\n
- Requirements management plan<\/strong> \u2014 also known as the business analysis plan, which defines how the requirements will be documented, managed, and analyzed, and how the changes will be handled.<\/li>\n<\/ul>\n\n\n\n
To properly plan scope management, it\u2019s necessary to perform a detailed analysis of:<\/p>\n\n\n\n
- \n
- Project charter<\/a>, <\/li>\n\n\n\n
- Project management plan<\/a>, <\/li>\n\n\n\n
- Organizational policies, and <\/li>\n\n\n\n
- Enterprise environmental factors.<\/li>\n<\/ul>\n\n\n\n
\n
\n\nAdvanced project management features<\/h2>\n
Nothing better than having all your work in one place. Try Plaky by CAKE.com today for free!<\/p>\n\n
\n Sign up<\/a>\n\n Learn more<\/a>\n <\/div>\n <\/div>\n\n\n\n \n ![\"Illustration\"](\"https:\/\/plaky.com\/learn\/wp-content\/themes\/cake-learn\/src\/images\/plaky\/banners\/features.png\")
\n <\/picture>\n <\/div>\n<\/div>\n <\/p>\n\n\n\n#2 Collect requirements<\/h3>\n\n\n\n
Project managers need to collect information from clients, sponsors, and other key project stakeholders<\/a> to determine and document their needs, wishes, and requirements regarding the project before defining the scope.<\/p>\n\n\n\n
Requirements are often collected through:<\/p>\n\n\n\n
- \n
- Interviews, <\/li>\n\n\n\n
- Surveys, <\/li>\n\n\n\n
- Questionnaires, <\/li>\n\n\n\n
- Focus groups, and <\/li>\n\n\n\n
- Benchmarking. <\/li>\n<\/ul>\n\n\n\n
Similarly to scope management planning, requirements gathering<\/a> can also be performed either once, at the beginning of the project planning, or at multiple agreed times throughout the project. Its main outputs are:<\/p>\n\n\n\n
- \n
- Requirements documentation<\/strong> \u2014 a document that states the requirements and describes how they fit within the project\u2019s business needs, and<\/li>\n\n\n\n
- Requirements traceability matrix<\/strong> \u2014 a grid that traces requirements from the beginning until completion. It helps ensure that all of the initially defined requirements are delivered in a satisfactory way at the end of the project. <\/li>\n<\/ul>\n\n\n\n
#3 Define the scope<\/h3>\n\n\n\n
Once the scope management plan is completed, and all the requirements are collected, it\u2019s time to define the scope.<\/p>\n\n\n\n
This is when the project manager creates the scope statement of work (SOW) \u2014 a document that will define the future development of the project.<\/p>\n\n\n\n
To help you kick off your project planning, we\u2019ve prepared a free editable scope statement template you can download below.<\/p>\n\n\n
\n![\"\"](\"https:\/\/plaky.com\/learn\/wp-content\/uploads\/2022\/02\/Plakys-project-scope-statement-template.png\")
<\/figure>\n<\/div>\n\n\n<\/div>\n\n\n\nGet our project scope statement template<\/a><\/p>\n\n\n\n
And if you prefer to fill out your templates with a pen, we\u2019ve also prepared a print-friendly version.<\/p>\n\n\n\n
Get our printable project scope statement template<\/a><\/p>\n\n\n\n
A good project scope statement should be comprehensive and clearly written. According to the S.M.A.R.T. goal-setting method, project objectives should be:<\/p>\n\n\n\n
- \n
- Specific,<\/li>\n\n\n\n
- Measurable,<\/li>\n\n\n\n
- Attainable,<\/li>\n\n\n\n
- Relevant, and<\/li>\n\n\n\n
- Time-based.<\/li>\n<\/ul>\n\n\n\n
![\"S.M.A.R.T.](\"https:\/\/plaky.com\/learn\/wp-content\/uploads\/2022\/02\/S.M.A.R.T.-goals-for-project-planning.png\")
S.M.A.R.T. goals for project planning<\/figcaption><\/figure>\n<\/div>\n\n\n #4 Create a work breakdown structure (WBS)<\/h3>\n\n\n\n
In the fourth phase of scope management, the project manager creates the work breakdown structure<\/a>, dividing larger chunks of a project into smaller sections that are easier to perform and manage. Essentially, a WBS is a thorough breakdown of the work that needs to be done to complete the project.<\/p>\n\n\n\n
The main outputs of this scope management process are:<\/p>\n\n\n\n
- \n
- Scope baseline <\/strong>\u2014 the approved versions of the scope statement, the WBS, and the WBS dictionary, and<\/li>\n\n\n\n
- Project document updates <\/strong>\u2014 all previously created documentation that needs to be updated.<\/li>\n<\/ul>\n\n\n\n
\n\ud83d\udca1 Plaky Pro Tip<\/strong><\/p>\n\n\n\n
To learn more about the scope baseline, check out our guide on the subject:<\/p>\n\n\n\n
- \n
- Baseline in Project Management: Everything You Need to Know<\/a><\/li>\n<\/ul>\n<\/div><\/div>\n\n\n\n
#5 Validate the scope<\/h3>\n\n\n\n
Scope validation refers to the approval of the final deliverables<\/a>. It\u2019s one of the most important stages in scope management as key stakeholders may request changes to the deliverables and give their official approval.<\/p>\n\n\n\n
The manager should make sure this process is carried out throughout the project after each deliverable is submitted. Delaying approvals could cause bottlenecks with other related deliverables.<\/p>\n\n\n\n
The main outputs of scope validation are:<\/p>\n\n\n\n
- \n
- Accepted deliverables<\/strong> \u2014 formal documentation that contains the list of approved deliverables and the signatures of all key stakeholders,<\/li>\n\n\n\n
- Work performance information<\/strong> \u2014 documentation explaining the project progress along with all the deliverables that were accepted or rejected,<\/li>\n\n\n\n
- Change requests <\/strong>\u2014 documentation listing the deliverables that have not been accepted and the reasons for their rejection, along with the formal change requests, and<\/li>\n\n\n\n
- Project document updates<\/strong> \u2014 all previously created documentation that needs to be updated.<\/li>\n<\/ul>\n\n\n\n
#6 Control the scope<\/h3>\n\n\n\n
Finally, scope control is performed continuously throughout the project in order to monitor it and manage changes. It also ensures that all change requests are first processed through the previously established change control process.<\/p>\n\n\n\n
This is an especially important step in scope management, and project management<\/a> as a whole, as it helps prevent scope creep<\/a>. Constant attempts to tweak or add requirements \u2014 without making corresponding adjustments to the budget and deadlines \u2014 can lead to scope creep and even project failure.<\/p>\n\n\n\n
The main outputs of scope control are:<\/p>\n\n\n\n
- \n
- Work performance information<\/strong> \u2014 describes the project\u2019s progress, its level of adherence to the scope baseline, and all the changes and their impact on the budget and schedule,<\/li>\n\n\n\n
- Change requests<\/strong> \u2014 a document consisting of formal, filled-out change requests,<\/li>\n\n\n\n
- Project management plan updates<\/strong> \u2014 all changes made to the main documents in the project management plan (scope management plan, scope baseline, schedule baseline, cost baseline, performance measurement baseline, etc.), and<\/li>\n\n\n\n
- Project document updates<\/strong> \u2014 all previously created documentation that needs to be updated.<\/li>\n<\/ul>\n\n\n\n
\ud83d\udcd6 Explore both basic and advanced project management terms in our Project Management Glossary of Terms<\/a> to master managing projects efficiently!<\/p>\n\n\n\n
Keep your project on the right track with Plaky by CAKE.com<\/h2>\n\n\n\n
Feeling overwhelmed?<\/p>\n\n\n\n
A project management tool like Plaky<\/a> by CAKE.com<\/a> can be invaluable in helping you complete your projects while avoiding scope creep.<\/p>\n\n\n\n
With its wide variety of project management features<\/a>, Plaky can help you:<\/p>\n\n\n\n
- \n
- Organize your workload and individual assignments in detailed items<\/a> to make sure your team is working on the agreed requirements,<\/li>\n\n\n\n
- Track progress and stay in the loop through comments<\/a>, <\/li>\n\n\n\n
- Facilitate efficient team communication<\/a> \u2014 no matter where your team is working from, and<\/li>\n\n\n\n
- Centralize document sharing<\/a> so that it\u2019s easier to keep an eye on project development and stay within scope.<\/li>\n<\/ul>\n\n\n
\n![\"Example](\"https:\/\/plaky.com\/learn\/wp-content\/uploads\/2022\/02\/Organizing-a-project-board-in-Plaky.png\")
Organizing a detailed project board in Plaky<\/figcaption><\/figure>\n<\/div>\n\n\n Even better, Plaky by CAKE.com offers a comprehensive free plan and many premium features in its affordable Pro and Enterprise plans. Plus, you can try out all of these features for 14 days for free!<\/p>\n\n\n\n
- Track progress and stay in the loop through comments<\/a>, <\/li>\n\n\n\n
- Change requests<\/strong> \u2014 a document consisting of formal, filled-out change requests,<\/li>\n\n\n\n
- Work performance information<\/strong> \u2014 documentation explaining the project progress along with all the deliverables that were accepted or rejected,<\/li>\n\n\n\n
- Accepted deliverables<\/strong> \u2014 formal documentation that contains the list of approved deliverables and the signatures of all key stakeholders,<\/li>\n\n\n\n
- Project document updates <\/strong>\u2014 all previously created documentation that needs to be updated.<\/li>\n<\/ul>\n\n\n\n
- Scope baseline <\/strong>\u2014 the approved versions of the scope statement, the WBS, and the WBS dictionary, and<\/li>\n\n\n\n
- Requirements traceability matrix<\/strong> \u2014 a grid that traces requirements from the beginning until completion. It helps ensure that all of the initially defined requirements are delivered in a satisfactory way at the end of the project. <\/li>\n<\/ul>\n\n\n\n
- Requirements documentation<\/strong> \u2014 a document that states the requirements and describes how they fit within the project\u2019s business needs, and<\/li>\n\n\n\n
- Project management plan<\/a>, <\/li>\n\n\n\n
- Requirements management plan<\/strong> \u2014 also known as the business analysis plan, which defines how the requirements will be documented, managed, and analyzed, and how the changes will be handled.<\/li>\n<\/ul>\n\n\n\n
- Scope management plan <\/strong>\u2014 a plan that defines how the scope statement and the WBS will be created, as well as how validation will be obtained, and<\/li>\n\n\n\n
- Goals<\/strong> \u2014 identifies what the project aims to achieve,<\/li>\n\n\n\n
- Justification<\/strong> \u2014 identifies the need for the project, <\/li>\n\n\n\n
![\"Illustration\"](\"https:\/\/plaky.com\/learn\/wp-content\/themes\/cake-learn\/src\/images\/plaky\/banners\/default@2x.png)
\n <\/picture>\n <\/div>\n<\/div>\n <\/p>\n\n\n\n![\"Illustration\"](\"https:\/\/plaky.com\/learn\/wp-content\/themes\/cake-learn\/src\/images\/plaky\/banners\/features@2x.png)
\n <\/picture>\n <\/div>\n<\/div>\n <\/p>\n\n\n\n