Project Name Project Kickoff Agenda Introductions Collaboration Project

‘ Project Name - Project Kickoff

Agenda • Introductions • Collaboration • Project team & roles • Risk, Issue, and Change Management • Scope • Reporting • Definition of success • Needs to get ‘started • Approach & Approval process • Q&A • High level Plan 2

‘ Introductions 3

‘ Project Teams 4

Project Steering Committee Name Title Project Role Sally Jones VP, Dept Name Project Sponsor John Doe SVP, Dept Name Dept Representation ‘ 5

Change Control Board Name Title Project Role Sally Jones VP, Dept Name Project Sponsor Ken Smith Director, Dept Name Dept Representation ‘ 6

Stony Brook Project Team Name Title Project Role John Passaro Senior Project Manager Andrew Kirsch Director, Enterprise App Integrations Technical Lead Ray Chan Director, Enterprise App Integrations Integration Lead Suzie Jones Asst. Provost Subject Matter expert ‘ 7

‘ Scope 8

Project Scope • The Stony Brook University will be implementing a Customer Relationship Management (CRM) system that will provide the Undergraduate Admissions department with an admissions and recruiting database, dynamic online applications, and a segmented multi-channel communications tool with reporting functionality. • This solution will also require integrations with our People. Soft student information system, for the transfer of student data. This solution will be replacing our home-grown ECM-based solution with a fully-functioning CRM system. The home-grown ECM-based solution will then be decommissioned. • The scope of this project is limited to implementation of a CRM tool for Undergraduate Admissions targeted at ‘ recruitment of traditional undergraduate students. • It includes research of best practices, engagement of professional services as needed, strategy development, process redesign, communications, and training. 9

Definition of success The project success criteria refer to measurable terms of what should be the outcome of the project that is acceptable to the end user, customer, and the stakeholders. In other words, the project success factors consist of activities or elements that are required to ensure successful completion of the project. • All integrations must be fully developed and tested. • Add a line regarding satisfying Security requirements. • The system must be available 99. 99% of the time. All servicing of the system must be done (add whatever the window is). • A qualified CRM application analyst must be available at the time ‘of configuration. • Admissions staff must be educated in building and leveraging the tool’s capability and in bestpractice recruitment strategies to: • • • Expand the prospect funnel Increase conversion rates of traditional first-time undergraduate enrollment Differentiate student segments to support diversity and quality 10

‘ Project Approach 11

Approach • It is suggested that this project will leverage the Waterfall project management methodology. This is a sequential, linear process that consists of several discrete phases. (Or replace with the planned approach) ‘ • There will be three sign off points during the Project; 1) Charter, 2) Requirements, 3) Implementation • The Project is currently in the Project Initiation Phase, during this Phase the Charter will be signed • During the Procurement Phase, the Vendor Management team will take the lead. 12

A 103_Project. Kickoff Approval Process • The project will have Milestones that will require Project Steering Committee approval. 1. Charter: documents the business needs, assumptions, constraints, the understanding of the customer's needs and high-level requirements, and the new product, service, or result that it is intended to satisfy, such as: Project purpose or justification. Measurable project objectives and related success criteria. ‘ 2. Requirements: detailed requirements which clearly outline the expected result of the Project. Clear distinction on how the system should perform, these functional requirements will help drive testing strategies. 3. Implementation Plan: documents the accumulation of the project activity including the test scenarios, test results, and support plan. This plan should outline all transitions that will occur. Approval if this plan is an approval to go live with the system. 13

‘ High-level Schedule 14

A 103_Project. Kickoff High-level Schedule ‘ 15

A 103_Project. Kickoff Collaboration • All pertinent Project details and artifacts will be posted to this Project site: Project Name - Documents • Monthly Status reports will be posted here: https: //it. stonybrook. edu/projects ‘ 16

A 103_Project. Kickoff Risk, Issue, and Change Management 1. The Risk log will be updated weekly and available to the team here: add link 1. The Issue Log will be updated weekly and available to the team here: add link ‘ 1. All Changes to scope, budget, resources, and time will go through the Change Management process. The change will be documented and submitted to the Change Control Board for review and a decision. All Changes will be logged in the Change Log here: add link 17

A 103_Project. Kickoff Reporting Name Target Frequency Format Location of Artifacts Monthly Status report All Stakeholders Monthly PDF https: //it. stonybrook. edu/projects Project Steering Committee PSC Members Monthly Meeting/PPT Add link to PPT here Core Team Meeting Project Team Weekly Meeting Posted Minutes here Status Communication Project Team Milestone based E-mail Change Request PSC Members As needed Meeting/PPT ‘ Add link to PPT & minutes here 18

A 103_Project. Kickoff Needs to move forward • What does the team need to do, provide, procure, etc to move forward? Outline the steps here. ‘ 19

A 103_Project. Kickoff Next steps • Highlight the next steps that the Project team will take. Such as close the Initiation Phase and start the Procurement Phase. Highlight what can be expected. ‘ 20

A 103_Project. Kickoff Questions and Comments ‘ 21