The objective of a Scope of Work (SOW) is to clearly define the project's deliverables, tasks, timeline, and responsibilities.
Scope
For all projects Internal and External
Purpose
It establishes a mutual understanding between the client and the company about the project's objectives, requirements, and constraints.
Components of Scope of Work (SOW)
The scope of work document primarily has the following components:
Project Overview
Actors
Proposed Technical Solution
Functional Requirements
Non-Functional Requirements
Constraints and Assumptions on both Functional and Non-functional Requirements
Project Deliverables
Project Timeline
Acceptance Criteria
Communication Plan
Risk Management Plan
Change Control Procedure
Quality Assurance Plan
Resource Team and Responsibility
Development Process to be followed
Payment Terms
Section 1: Project Description
Project Summary
The client looking for a platform where customers and employees can communicate with each other with the utmost ease and Admin can track all the vital information.
Platform Users (Actors)
The platform has only three actors
Employees: a short description of user type
Customers: a short description of user type
Admin: a short description of user type
Proposed Technical Solution
Based on the requirement and preferences shared by the client, Relinns Proposes to develop a web and mobile-based application for the end users & employees to achieve the above-mentioned project goal.
Client Engagement
Relinns Technologies (hereafter referred to as the Company) will work with the client and team to build a solution with features in line with the SOW broken down in the next section.
Section 2: Functional Requirements
End User Application (Android, iOS & Web)
Email Authentication
Ability to log in using the credentials provided by the company
Ability to remember me. It will help user to log in easily in future
Multi-factor Authentication
a. Phone Number Verification:
Users must be able to register and verify a valid phone number associated with their account.
The system should send a one-time verification code via SMS to the registered phone number.
Users should have the option to request a code again in case SMS delivery fails.
b. Google Authenticator Integration:
Users should have the ability to link their accounts with the Google Authenticator app.
The system should generate a QR code for each user to scan with the Google Authenticator app for setup.
The Google Authenticator app should generate time-based one-time passwords (TOTPs) for the account.
c. MFA Enrollment and Management:
Users must have the option to enroll in MFA voluntarily but should be encouraged to do so.
The system should provide users with the ability to enable, disable, or modify their MFA settings.
Administrators should have the capability to enforce MFA for specific user roles or groups.
Assumptions
These are not the final requirements and will change after the client reviews the same.
Not in scope
Anything which is not explicitly mentioned in Section 2 will not be part of the scope.
Section 3: About Relinns Technologies Pvt Ltd
3.1 About Relinns
Established in 2016, Relinns Technologies has developed and published over 100 mobile applications in Google Play and Apple App Store.
At Relinns, we breathe tech solutions and embrace innovations with open arms. With over 3 years of experience, we have had phenomenal growth which acts as a testimony to the knowledge we have come to gather over time.
3.2 About AppsRhino
AppsRhino is a Relinns Technologies product that powers on-demand apps and business apps for entrepreneurs and enterprises
Section 4: Project Team
Project Manager
Graphic Designer
Developer
UX Designer
QA
Subject Matter Expert
The actual Scope of work will also have the responsibility of each of their roles and number of resource allocated.
Section 5: Process and Tools and Technologies
As each customer is unique in themselves and wants to solve any problem in unique way, hence, This section is usually custom based on the needs of clients and requirements for the project. This section will have information of
Development Process
Tools to be used
Technologies to be used
Communication Plan
RACI Matrix
Deployment Design
Planned deployment Design
Planned Physical Architecture
Planned Application Environments
Non-function requirements and Assumptions
Section 6: Project Timeline & Deliverables
This section also varies based on the client's market go-live plans. It will be a milestone-based delivery plan along with all the deliverables.
Section 7: Project and Maintinance Cost
This section also varies based on the client's functional and non-functional requirements. It will be a milestone-based payment plan along with all the deliverables. This section primarily has the following info
Project Development cost
Payment Milestones for custom development
Hosting Infra Cost
The cost associated with 3rd party Integrations (Optional)
Section 8: Maintenance & Support
This section also varies based on the client's functional and non-functional requirements. This section primarily has the following info
