Last update: April, 2017. Wrike, Inc.
This Statement of Work ("SOW") is incorporated into the SAAS Subscription Agreement (the "Agreement") between Wrike, Inc. ("Wrike") and Customer, dated Effective Date of the Agreement. If any terms of this SOW conflict with the Agreement, the Agreement's terms and conditions shall control.
Wrike and the Wrike Professional Services (“PS”) team presents Customer with this SOW for deployment-related consultative services. The goal of this engagement is to provide concentrated sessions to ensure that Customer successfully implements Wrike tools in support of Customer’s work management requirements. This engagement between Customer and Wrike will be accomplished by consultative services provided by the Wrike PS team remotely.
The purpose of this document is to describe the scope of work, resources, and high-level tasks for Wrike and Customer to accomplish in a successful outcome for this engagement.
Wrike will work with Customer to implement its deployment methodology (below) in the context a Deployment engagement. The planned start date must be within thirty (30) consecutive days from the signature date of the Agreement. The Professional Services will be deemed delivered within sixty-five (65) consecutive days of the Effective Date of the Agreement. The Wrike Deployment Methodology is summarized below and described in detail on the Wrike Deployment web page:
Step 1. KickoffThis first call will cover all things needed for a successful implementation of Wrike. Let’s get started!
- Identify champion team
- Define 90 day goal
- Clarify Wrike's usage scope
- Determine Launch Day
Step 2. Process MappingIt’s time to dig into your work and how to use Wrike! What types of projects do you do? How do projects start/end? Your processes will be examined and defined.
- Define and input clearly defined processes in Wrike
Step 3. Workspace SetupLet’s get into the look and feel of your day-to-day in Wrike. We'll focus on the overall design of your team’s workspace.
- Establish folder structure
- Establish at least 1-3 projects
- Add users
- Create groups
Step 4. Workfow TrainingTime to transform your champions into bona fide Wrike ninjas! This training will demonstrate key features needed to get work done.
- Entire champion team can explain your new Wrike process
Step 5. Change Management PreparationChange can be difficult, but we'll help you. This time is for developing a rollout strategy, answering final questions, and helping incentivize your team to use Wrike.
- Define 'Rules of Wrike'
- Set 'Wrike Introduction' meeting date
- Complete internal training plan
Step 6. User TrainingAll aboard: it's time for all users to learn Wrike! This traning teaches users how to do work in Wrike and build day-to-day Wrike habits.
- View introductory videos prior to training
- Verify team can start, execute, and complete work in Wrike
- Set up all personal profiles
Step 7. Launch PreparationAlmost there — let's make sure everyone is ready for a successful launch! Please use the provided launch preparation checklist.
- Review all checklist items
- Confirm champions are able to onboard new users
Step 8. LaunchCongratulations, we made it! Use the first week in Wrike to gather feedback, engage users, and help everyone rethink how work is done.
Wrike utilizes a collaborative process in its deployment methodology. While trying to ensure efficient involvement of both Wrike and Customer resources, it is still imperative to have appropriate resources involved in the deployment.
3.1. Planned Customer Resources
|Deployment Lead||Knowledgeable about the overall program and process methodologies. Also, Customer resource responsible for marshaling Customer resources and for project sign off.|
|Deployment Team||Customer team members tasked with Wrike rollout and who will be day-to-day Wrike users.|
|Champion Team||Key members of the Customer Deployment Team with a stake in the process and who provides input into Discovery and training sessions.|
|Sponsor||Customer team member responsible for overall direction regarding process refinements and who either selected or approved the use of Wrike.|
- Customer will provide access to subject matter experts and decision makers to provide critical path project decisions in a commercially reasonable and timely manner. If input is not provided in a timely manner, a change order for material project impacts will be submitted to Customer.
- Project milestones will be based on availability of Customer resources and key decision makers. Lack of access to the project stakeholders can impact project timelines and cost.
- If Customer has additional requirements that are not included in this SOW, Wrike will provide a separate SOW and price estimate for the additional services.
- The staffing for this project will occur upon the signing of the Agreement. Before the acceptance of the Agreement, no staffing will be scheduled or allocated. The planned start date must be within thirty (30) consecutive days from the signature date of the Agreement. This advanced notice is needed to provide Wrike with enough time to allocate appropriate resources to start the project on time.
- Delays resulting from Customer’s inability to meet the foregoing project assumptions will be defined as “Project Delays.” Professional Services that are not delivered within sixty-five (65) consecutive days of the Agreement Effective Date as a result of Project Delays will be deemed delivered.
Wrike is pleased to present this proposal for this project that includes the scope of work defined in this document.
The fee for this engagement is listed in the Agreement.
Wrike does not foresee expenses for this virtually-delivered engagement. However, should the need forexpenses arise, Wrike will first receive written consent and then bill Customer for actual expenses arising from this effort.
By signing the Agreement Customer certifies that Customer has reviewed this SOW and agrees to be bound by terms and conditions laid herein.