Onboarding Statement of Work

This Statement of Work (this “SOW”) is entered into and governed by the Master Subscription Agreement, Subscription Terms, or other similar written agreement (the “Agreement”), along with the General Service Terms located at harness.io/legal (the “General Terms”) by and between Customer (“Customer”), and Harness Inc. (“Harness”) (Customer and Harness each a “Party”, and collectively, the “Parties”).  This SOW and the General Terms constitute the complete agreement regarding services provided under this SOW.  Except where the contrary is expressly provided, the terms and conditions of 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 General Terms.

1. PROJECT OVERVIEW

The purpose of this Onboarding SOW is to provide services designed 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. Customer must be committed to deploying the use case during an agreed upon number of sprints.  The standard timeline for the entire SOW is set forth below), and will consist of a series of sprints, to be finalized with project management.  Each project begins with an initiation phase that will produce the  Implementation Design Document and Project Plan and validate the contents with the Customer.

2. TIMELINE; SCOPE OF PROJECT; SPRINT DETAILS

Timeline for Onboarding Sprints (as applicable)

* Any exceptions will be noted in the module appendix

Kickoff and Sprint Planning Details

Implementation Design Document:

• Delivered within five Business Days of the completion of the Project Initiation activities described above.
• The Implementation Design Document may contain the following, as appropriate:
  • A high level installation architecture and design for the Product
  • The prerequisite software and personnel to support the pProject
  • Prioritized tasks and deliverables
  • May highlight risks/issues and/or blockers that put the timelines at risk
  • Prerequisites / tasks to be completed by the Customer before Implementation sSprints can begin, including providing the required people that must be available during the Sprint timelines.
• The Project Plan may contain the following, as appropriate:
  • Project dates and 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.
  

Project Sprint(s):

Sprints help ensure the use cases as documented and agreed upon in the Implementation Design Document is delivered. The sSprint timelines will be defined and prioritized in the Project Plan.

Customer Sprint Prerequisites

• Customer agrees that it will complete the following prior to the start of any sSprints:
  • Review and approval of the Implementation Design Document
  • Completion of implementation prerequisites set forth in the Implementation Design Document

Sprint Activities

Account & 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 one (1) supported encrypted secret storage provider (as applicable)
    

Adoption

• 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 the Implementation Design Document
  

Project Completion:

• Project implementation is complete and accessible by the Customer as defined in the relevant Module Appendix
• Updated Implementation Design Document:
  • 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 Project  (which not in scope for this SOW)