Adoption 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 “Agreement”) 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

This SOW covers services intended to provide engineering expertise with respect to utilizing the Harness Platform and the software modules licensed, and as deployed, by Customer (the “Solution(s)”), including consulting with the Customer in connection with Customer’s deployment, management and integration of Solutions in Harness production and Non-Production Environments. An Adoption Program project team will be assigned to the Customer account to provide strategic and tactical guidance on Customer processes and initiatives with respect to cloud transformation utilizing Harness Solutions.

2. TIMELINE; SCOPE OF PROJECT; SPRINT DETAILSTimeline for Adoption Sprints (as applicable)

During the term of this Statement of Work, Harness will assist Customer in planning and executing the following activities:

‍Architecture Design and Reviews: The parties will collaboratively design the architecture for Customer’s Harness Solution and adoption use cases. Harness will review and provide feedback on existing architecture designs under use and seek to align architectural decisions with organizational goals and standards.

• Adoption management of additional user-based adopter teams onto Harness from initial onboarding program, and adoption of additional use cases onto Harness solutions,  that fall within the scope found in the applicable Module Appendix
• Guided white boarding sessions on adoption plan management
• Guided configuration for adoption plans and enablement plans
• Guided configuration for net new adoption use cases or adoption focused use cases
• Assisted facilitated workshops for groups to use the Harness Solutions

Module Adoption Workstreams: The parties will confirm and plan specific module adoption goals and objectives to be described in the Implementation Design Documents as part of the overall adoption program, during the Statement of Work term. Specific scope to be implemented during the adoption program to be found in the applicable Module Appendix.

Implementation Design Document Updates: The parties will ensure that architecture diagrams, design decisions, and usage guidelines are well-documented.

Technical Mentoring: Harness will offer technical mentorship over the course of the term of the Statement of Work and help users understand and implement Harness module architectural patterns, best practices, and solution standards.

Kickoff and Sprint Planning Details

Implementation Design Document:

• Delivered within five (5) 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 project
  • 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 sprints 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 sprint 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 sprints:
  • 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)