Project Scope Document - Template example
Table of Contents
PROJECT SCOPE SUMMARY |
---|
Phase 1 The scope of the <project name> project is implementing <XYZ> and other items considered in-scope in table below. It is expected that all in scope items will be implemented in phases leading up to, or within, the final go-live phase (listed in the milestone table). Phase 1 of the project will begin <mm/qq/yyyy> and complete by <mm/qq/yyyy>. The remaining phases of the project will be implemented (include if applicable) Out of scope items are also listed in the table below. All out-of-scope items may be considered for a future, separate, new features & enhancements project. Scope Change. If new items come up during the process of implementation and need a decision to add to or cut from scope, the team will need to go through the scope change request process. Considerations during its evaluation through the scope change process may include the item’s relation to what is currently in-scope, if it will negatively impact the project’s timeline to completion, resource allocations, or not considered critical path for solution functionality. |
IN SCOPE/OUT OF SCOPE
ITEM | IN-SCOPE | OUT-OF-SCOPE | ADDITIONAL INFORMATION | |
---|---|---|---|---|
1 | Organizational Change Management |
|
|
|
2 |
|
|
|
|
3 |
|
|
|
|
4 |
|
|
|
|
5 |
|
|
|
|
SCOPE CHANGE PROCESS
Include visual for scope change process (image below is an example- please replace with applicable process) |
ADDITIONAL RESOURCES
Decision log entry for including course and program approval in scope: <ADD ITS-Pro link for “Decision Log>