This Statement of Work (this “SOW”) is entered into and governed by the Master Services Agreement (the “Agreement”) by and between Customer and Harness as of the last signature and subject to an executed Harness or Sales Partner’s Order Form with Customer for a Product (as defined below) with a valid reference to Professional Services (“SOW Effective Date”). This SOW and the Agreement constitute the complete agreement regarding Professional Services provided under this SOW. Except where the contrary is expressly provided and in compliance with Agreement Section 14.14 “Entire Agreement”, the terms and conditions of the Agreement and the General Terms shall prevail over any conflicting terms or conditions in this SOW.
Any defined terms not specifically defined herein shall have the meaning given to them in the Agreement.
1. DEFINITION
“Project Summary” means a summary of the work completed under this SOW, which will be created by Harness upon completion of the Sprints.
2. PROJECT OVERVIEW
This Onboarding SOW provides Professional Services to assist Customer in deploying the applicable Harness software Module, based on best practice, reference architecture and appropriate use cases as defined in the Module Appendix. The use case selected must be (i) achievable within the project timeline, (ii) derive a first value for the Customer, and (iii) Customer must be committed to deploying the use case during an agreed upon number of sprints (each, a “Sprint”). The standard timeline for the entire SOW is set forth below, in Service Weeks (the “Project Duration”), and will consist of a series of Sprints, to be finalized with Customer’s project management in the engagement. Each Project begins with a Design and Discovery Review based on scope validated from the Technical Program Management scoping process prior to Professional Services engagement commencing, followed by one or more Sprints as applicable.
Harness will provide a qualified Personnel team, including an Implementation Services Engineer (the “ISE”), and Technical Program Manager (the “TPM”) who will work with the Customer during the Sprints, to implement and deliver the Project as described in this SOW.
The Onboarding SOW provides Customer with a high-level configuration of the use cases defined in the Module Appendix, and modeled after a Harness Reference Architecture. Upon completion of the Project, engagement details will be documented in the Engagement Document by Harness to provide the Customer with an ability to extend to Customer teams, including those beyond the pilot groups as part of the implementation plan.
3. TIMELINE; SCOPE OF PROJECT; SPRINT DETAILS
Timeline for Onboarding Sprints (as applicable)
Scope of Project and Onboarding Kickoff
The procedures set forth below and in the appendices (as referenced) apply to the duration of this Onboarding SOW, for the implementation and onboarding of the Product. This SOW includes (A) Platform Setup Scope, and (B) Module Onboarding Scope, for the agreed upon use cases.
The SOW shall begin with a Kickoff meeting and adhere to the General Service Terms. The outcome of this meeting should result in the scheduling of the Discovery & Design Review from the Presales workshops that were completed prior to this engagement.
Kickoff and Sprint Planning Details
Onboarding Deliverable: Agreed Upon Onboarding Project Plan
- Delivered within one Service Week of the completion of the Kickoff activities described above.
- The Project Plan may contain the following, as appropriate:
- A high level installation architecture and design for the Product
- The software and staff prerequisites to support the Project
- Project dates and timelines, defined by sprint outlining prioritized tasks and deliverables
- Will highlight risks/issues and/or blockers that put the timelines at risk
- Prerequisites / tasks to be completed by the Customer before implementation Sprints can begin, including providing the required people that must be available during the Sprint timelines.
- The Project Plan will be available via the Harness Professional Services Portal (a link to this Portal will be provided) for Customer to view and track Customer’s participation throughout the term of this SOW.
Acceptance Criteria for Deliverables; Acceptance Process:
- The Customer will have five (5) Business Days after receiving the Project Plan writing from Harness to review the Project Plan and provide feedback and approval or rejection. If the Customer rejects any aspect of the Project Plan, the Parties will work together in good faith to address the issue(s) and an updated Project Plan will be provided for review and Customer will have an additional five (5) Business Days to review the revised Project Plan. This approval cycle will continue up to (2) times, or until the Project Plan has been approved by Customer, whichever comes first.
- If, after having received the Project Plan from Harness in writing, Customer does not provide an affirmative approval or rejection of the Project Plan during the five (5) Business Day review period, or after the second approval cycle, the Project Plan shall be deemed accepted.
- Implementation Sprints will not be scheduled until the Project Plan is approved. Once approval is provided, the Implementation Sprints will be scheduled. Harness requires up to three (3) Business Days to finalize the scheduling for the Implementation Sprints.
Implementation Sprint(s):
The Implementation Sprints will ensure the Project Plan, as documented and agreed upon in Discovery & Design Sprint, is delivered. The Implementation Sprint timelines are defined and prioritized in the Project Plan.
Customer Prerequisites
- Customer agrees that the following will be completed prior to the start of Implementation Sprints:
- Review and approval of the Project Plan
- Completion of implementation prerequisites set forth in the Project Plan
Platform Setup (as applicable)
- Single Sign-on integration with one (1) supported Identity Provider
- Implement the Initial Account Hierarchy
- Configure Persona-based RBAC
- Secret Manager integration with up to (1) supported Encrypted Secret Storage Provider (as applicable)
Onboarding
- Implementation of the Product based on the architecture and design outlined in the Project Plan, and based on the best practice scope relevant to the applicable Product (as outlined in the relevant Module Appendix reference with the Customer Order Form).
Customer Validation
- Review implementation with Customer administrators / architects
- Review implementation with Customer team
- Successful production-grade Product implementation for Customer team, with verification of success via KPIs agreed upon in Project Plan
Calibrate for Adoption
- A phase of activities that include:
- User Training & Enablement
- Self-service user Onboarding
- Automated Org and/or Project Onboarding
- Automated Resource Configuration
- Adoption of pre-configured templates
Deliverables
- Product implementation is complete and accessible by the Customer as defined in the relevant Module Appendix
- Knowledge transfer of the services rendered as part of this SOW.
- Creation of Project Summary:
- Customer specific notes about installation, configuration, and adoption of the Product
- Important findings during implementation
- Additional recommendations the Customer may wish to perform after the engagement (which not in scope for this SOW)
4. RESPONSIBILITIES; LIMITATIONS
Customer Responsibilities:
- Customer acknowledges and agrees that Harness’s ability to deliver the Services is dependent upon Customer’s full and timely cooperation with Harness, as well as the accuracy and completeness of any information and data Customer provides to Harness. In addition to the provisions of the Agreement, Customer will promptly: complete their required prerequisites set forth in the Engagement Plan. These prerequisites may include, but are not limited to:
- Permissions to manage cloud/on-premise infrastructure
- DNS entries
- TLS Certificate and related keys
- Cloud/on-prem network and/or proxy configuration, if needed
- Airgap systems, if needed
Limitations/Exclusions: Customer acknowledges and agrees that following limitations apply to this SOW:
- The single Module Product implementation will be limited to one (1) Customer Team
- Single Sign On configuration leveraging a non-tested Identity Management Platform that supports the SAML 2.0 standard can only be accommodated on a “best effort” basis and is not guaranteed. Customer’s EntraID Singe-Sign On mechanism is supported.
- Customer will ensure the availability of its Identity Management Platform administrator to make necessary changes outside of the Product when configuring Single Sign On.
- Governance Policies delivered as part of this engagement will be sourced from out-of-the-box examples, and any needed modifications can be accommodated on a best effort basis only and are not guaranteed.
- Customer is responsible for any system integrations that are not supported by out-of-the-box integrations.
5. FEES AND EXPENSES
Customer shall pay to Harness the fees set forth in the applicable Order Form and in accordance with the Agreement.
6. TERM AND TERMINATION
This SOW shall terminate upon the earlier of (i) six (6) months from the SOW Effective Date, or (ii) completion of the Services described above. The Parties may adjust the termination date of this SOW by executing a Change Order as stated in the General Service Terms section 7 “Change Orders”.
IN WITNESS WHEREOF, the Parties have read this SOW, understand its terms and conditions, and agree to be bound by them. They have caused this SOW to be signed through their respective duly authorized representatives and to be effective as of the SOW Effective Date.
Harness Inc. Customer
By: By:
Name: Name:
Title: Title:
Date: Date: