Kittitas County SOW Microsoft Purview Data Security Strategy PSA v4 20260929

Home Browse Search

Statement of Work September 29, 2026 - Version 4.0 Microsoft Purview Data Security Strategy Page 6 The Project will be managed using formal project management methodologies consistent with the Project Management Institute Project Management Body of Knowledge (“PMBOK”) framework. The following is a list of tasks which will be performed to manage the Project: Project Initiation • Facilitate Project kick-off meeting to review objectives, Scope, budget, Deliverables, timeline, and success criteria • Identify initial assumptions, dependencies, critical path items, and constraints Project Planning • Verify Client specific details including service hours, maintenance process(es), and administrative requirements • Establish communication plan (“Communication Plan”) to be executed throughout the Project • Work with technical team(s) to establish an approved detailed Project Plan/Schedule Project Execution • Drive and manage Project tasks per established Project Plan • Facilitate scheduling for on-demand meetings to support Project efforts Control and Monitoring • Risk and issue management to identify and manage risks, execute established mitigation plans, and facilitate resolution of Project execution issues • Financial management – monitor and manage Project budget (Labor, T&E, misc.) • Establish a one-page Project overview summarizing Project health and status • Confirm Client acceptance at the end of each milestone or Deliverable • Conduct weekly status meetings to deliver communication on the current Project health and status to Project stakeholders • Provide weekly status reports to document and communicate Project health and status Closure • Confirm Client’s acceptance of Project Completion 2.3 OUT OF SCOPE The following items are outside the scope of Deliverables contemplated by this SOW: • Large-scale site restructuring, if required, not listed in the Scope of Work section of this SOW • Data migration or protection services not clearly detailed within the Scope of Work section of this SOW • All levels of support not specifically detailed within the Scope of Work section of this SOW • Working on open maintenance and support issues unless the maintenance and support case and remedial efforts towards resolution are explicitly defined in this SOW • Any specific task or Deliverables not clearly stated in the Scope of Work section of this SOW Any mutually agreed upon changes to the Scope of Services shall be set forth in a Change Request Form as detailed in the Project Change Process section below. 2.4 PROJECT CHANGE PROCESS Trace3 is not responsible for issues out of its control, which sometimes includes Client unpreparedness, technical issues (based on Client responsibilities in this SOW), manufacturer bugs (code issues), hardware failures after forty -eight (48) hour burn-in, or additional features desired (not outlined in this SOW). Changes in Services requirements to this SOW or issues out of Trace3’s control will require a written Change Order, submitted and signed by both Parties, and billed in addition to the Fees outlined in this SOW.