ARBITRAGE FINANCIAL

PROJECT SCOPE
January 10, 2023

OVERVIEW

1. `Deliverables

2. Affected parties

List business processes or systems which will be impacted by this project and describe how they will be affected.

3. Affected business processes or systems

Describe any specific components of the processes or systems that may be affected by this project.

4. Specific exclusions from scope

Describe any specific components that are excluded from this project.

5. Implementation plan

Describe how you plan to implement the project. For example, will all parts of the project be rolled out at once or will it be
incremental? What will be included in each release?

1
 6. High-level timeline/schedule

Describe what the high level timeline/schedule will be to plan, design, develop and deploy the project. Generally, by when do
you expect this project to be finished?

APPROVAL AND AUTHORITY TO PROCEED

Name Title Date

Approved By Date Approved By Date

ARBITRAGE FINANCIAL
PROJECT SCOPE
January 10, 2023

OVERVIEW

7. Project background and description

Describe how this project came about, who is involved, and the purpose.

Note: To delete any tip (such as this), select it and start typing. If you’re not yet ready to add your own text, select a tip and
press spacebar to remove it.

8. Project scope

Project scope defines the boundaries of a project. Think of the scope as an imaginary box that will enclose all the project
elements/activities. It not only defines what you are doing (what goes into the box), but it sets limits for what will not be done
as part of the project (what doesn’t fit in the box). Scope answers questions including what will be done, what won’t be done,

2
 and what the result will look like.

9. High-level requirements

Describe the high level requirements for the project. For example:

The new system must include the following:

• Ability to allow both internal and external users to access the application without downloading any software
• Ability to interface with the existing data warehouse application
• Ability to incorporate automated routing and notifications based on business rules

10. Deliverables

List agencies, stakeholders or divisions which will be impacted by this project and describe how they will be affected by the
project.

11. Affected parties

List business processes or systems which will be impacted by this project and describe how they will be affected.

12. Affected business processes or systems

Describe any specific components of the processes or systems that may be affected by this project.

13. Specific exclusions from scope

Describe any specific components that are excluded from this project.

14. Implementation plan

Describe how you plan to implement the project. For example, will all parts of the project be rolled out at once or will it be
incremental? What will be included in each release?

3
 15. High-level timeline/schedule

Describe what the high level timeline/schedule will be to plan, design, develop and deploy the project. Generally, by when do
you expect this project to be finished?

16. High-level timeline/schedule

Describe what the high level timeline/schedule will be to plan, design, develop and deploy the project. Generally, by when do
you expect this project to be finished?