Project Discovery – <Project Name >

1. Project Discovery – <Project Name> Most updates will only have 30 minutes maximum for their presentations. At least 10 minutes should be left for Q&A.

2. Purpose and Intended Outcome Purpose • To officially kickoff the Project: X • To present a high-level, conceptual plan Intended Outcome • To validate the documented approach and to formally launch the project into planning This presentation assumes the project team has put significant thought into objectives, goals, KPIs, staffing and implementation framework

3. Project Vision • Slide should be updated with project vision • IAM Vision added for reference and should be updated The Vision for Identity and Access Management (IAM) Provide secure access to applications that is easy for the user, application owner, and IT administrative staff with solutions that require fewer login credentials, enable collaboration across Harvard and beyond, and improve security and auditing Strategic Objectives Guiding Principles Key Performance Indicators • To simplify and improve user access to applications and information • To enhance critical business processes like onboarding, and automate where appropriate • To facilitate interschool collaboration and encourage external partner trust • To improve the security stature of the University with a standardized approach • Business needs should drive how the technology supports the identity and access management needs of the University • The tactical planning should remain aligned with the strategic objectives • Solution design should allow for other schools to use the foundational service or communicate with the service in a consistent, federated fashion • Communication and socialization of the program are critical to its success • Adoption rate of application integration with IAM, including federated components • Onboarding and deprovisioning process speed measurements, including number of resource objects being measured by the formal provisioning process • Number of Harvard schools that trust each other over time, and the number of trust relationships established with external partners • Adoption of InCommon Assurance Standards and InCommon Audit results

4. Scope

5. Before and After

6. Core Project Delivery Team • Sponsor: • Project Manager: • Technical Lead (if applicable): • Working Team: • Oversight Group (if applicable):

7. High-level Plan and Workstreams Update as necessary This is slide is not meant to convey the detail of a project plan. As such it should not be crowded but only provide a high level overview and should not be a crowded slide It should be a top down visual to provide high-level timing for executive leadership.

8. Next Steps / Milestones

9. Questions and Answers? • Does this approach, objectives and next steps align with the expectations of the governing body? • Do the milestones and next steps meet expectations? • Other Questions? • Please leave at least 10 minutes for Q&A • An update presentation should, at a minimum, ask the governing board to validate the approach and provide guidance and input

10. If necessary add additional slides beyond this point to support the update and to assist with pre-reading. If unnecessary, please delete this and next slide. Supporting Materials

11. Appendix A: <Title>