Project Plans

	PLAN	AREA(S) OF RESPONSIBILITY	DESCRIPTION	ITS Standard	COLLAB LINKS

	PLAN	AREA(S) OF RESPONSIBILITY	DESCRIPTION	ITS Standard	COLLAB LINKS
1	go-Live REQUIREMENT Risk Management Plan	pmocm Business/Functional Technical	Identifies risks, mitigation strategies, contingency plans Tracks risks, risk health, and statuses throughout the entire lifecycle of the project	ITS standard is for any and all project team members to identify and create risks. If risks are not mitigated in time, they turn into issues. Risks with a score of 9+ and issues with a score of 6+ are escalated through the project specific governance/escalation structure. Project manager is responsible for that escalation and any needed communication. Best practice is for a project to have at least one dedicated risk and issue identification session with the project team. For large and extra large projects, recommended to have session at the start of each major phase.	https://ucsdcollab.atlassian.net/wiki/spaces/SISCM/pages/395412192
2	Data Migration/Conversion Plan	Technical	Data conversion/migration is the process of translating data from one format to another. It involves the planning of steps and mapping of data fields to convert one set/type of data into a different, more desired, format.		https://ucsdcollab.atlassian.net/wiki/spaces/SISCM/pages/398328270
3	Environmental Management Plan	Technical	Identifies the what and how environments will be managed Hardware Software Dev spaces Sandbox, etc Supports the Testing Plan May even be included in the Testing Plan, in lieu of separate plan development, depending on the size of the project and level of detail of the Testing Plan		https://ucsdcollab.atlassian.net/wiki/spaces/SISCM/pages/397214186
4	go-live REQUIREMENT Reporting Plan	Business/Functional Technical	Defines reconciliation and remediation between the current state and the future state Determines what reports need to be developed for go-live or shortly afterwards Determine data/metrics that will be capture Determine if the reports will be from out of the box or activity hub(s) Determine what format it will be created and delivered (CSV, SQL, Cognos, Tableau, etc)	When only single system data is required and that tool has reporting functionality, reports should be created directly out of that system. If blended data is required, reports should be created from the AHs. ITS is responsible for AH infrastructure and data, and the business is responsible for creating and maintaining their reports.	https://ucsdcollab.atlassian.net/wiki/spaces/SISCM/pages/397214863
5	go-live REQUIREMENT QA/Testing Plan	Technical	Quality Plan >> Processes necessary to assure compliance with the requirements are defined Test Plan >> Defines testing team’s test strategy, goals, and scope Define the release scope Schedule testing timelines Define test objectives Determine test deliverables Design the test strategy Plan test environment and test data		https://ucsdcollab.atlassian.net/wiki/spaces/SISCM/pages/395051679 https://ucsdcollab.atlassian.net/wiki/spaces/SISCM/pages/398099091
6	go-live REQUIREMENT End User Training Plan	ocm Business/Functional	Identifies training objectives for the project/program, strategy for training and schedule for training initiatives. Assists in ensuring stakeholders receive the training they need when they need it. The training plan must give the different audiences what they want. A training plan is a living document that is created while the project/program is in planning. It will be monitored and executed during project planning, execution, and closure.		https://ucsdcollab.atlassian.net/wiki/spaces/SISCM/pages/399771877 https://ucsdcollab.atlassian.net/wiki/spaces/SISCM/pages/397607353
7	go-live REQUIREMENT Go-Live Deployment Plan	pmocm Business/Functional Technical	Deployment plans document the goals, timeline, initial identified tasks leading up to, including and after Go-Live. There can be other related docs/plans to the go-live deployment plan, such as: Go-live readiness criteria checklist Cutover plan Contingency plan (only used if not using checklist and cutover)		https://ucsdcollab.atlassian.net/wiki/spaces/SISCM/pages/495026177 https://ucsdcollab.atlassian.net/wiki/spaces/SISCM/pages/397837695
8	go-live requirement Hypercare Plan	pmocm Business/Functional Technical	Hypercare is the service of providing intense system support between the time of go live and project closure; as it relates to what was implemented in the project Often cover quick turn around issues/bug fixes related to standing up the system or what was agreed in the project scope and requirements Hypercare plan does not cover enhancement requests unless critical to the basic functions of the system implementation Plan should help clarify some of these items What is the ramp-up plan after initial Go Live? How long is hypercare expected to last? How much resource support will be expected? What are the responsibilities of all internal and external parties? Are there enough resources to support these expectations? What is the escalation plan and protocol during hypercare? What is the plan to transition from hypercare to long-term support?		https://ucsdcollab.atlassian.net/wiki/spaces/SISCM/pages/398131800
9	Deprecation/Decommission Plan	Technical ocm	Sometimes referred as sunsetting plan Identifies The process(es) and/or products/services that will be replaced by the project new implementation Timeline through deprecation and ultimately decommissioning Impacted units roles and responsibilities Activities to perform Security risks, if any Potential change management May include Impact analysis of deprecating old/existing product/service Cost analysis		https://ucsdcollab.atlassian.net/wiki/spaces/SISCM/pages/826048807
10	go-live requirement Service Transition Plan	ocm Business/Functional Technical	Service transition is the process of moving the project from project to service May include Sustainment Plan Continuity Planning Decommissioning Any OCM tasks to support the transition		https://ucsdcollab.atlassian.net/wiki/spaces/SISCM/pages/398361145 https://ucsdcollab.atlassian.net/wiki/spaces/SISCM/pages/398099194
11	PPMO REQUIREMENT Project Plan	pmocm Business/Functional Technical	For this project, the document that may also be referred to the OTL. The data will be in Jira but the project may be using Smartsheet to manage In the early stages of the project, an estimations worksheet may be used to identify initial deliverables, tasks, and hours. After initial project estimations are reviewed, information will be loaded into Jira May be linked to Project Charter Project Scope Document (detailed) Vendor Management plan >> https://ucsdcollab.atlassian.net/wiki/spaces/SISCM/pages/740360302		https://ucsdcollab.atlassian.net/wiki/pages/resumedraft.action?draftId=870612993&draftShareId=a3a9be5b-aed1-47b0-818b-5f720d0b88ea https://app.smartsheet.com/sheets/ch2QpMQ2Cp9VxpW6CFg34CFWcHrfj9x5CWP8hjM1
12	go-live requirement Project Change Management Plan	ocmBusiness/Functional	A change management plan defines activities and roles on how to manage and control change when implementing change in an organization as a result of implementing this project. May include List of the changes Responsibility assignment matrix, including stakeholders. Change roadmap, with a timeline for implementing each change Communication plan This project will be working under an OCM strategy that is comprised of many different plans		https://ucsdcollab.atlassian.net/wiki/spaces/SISCM/pages/395316106
13	Project Resource/Budget Plan	pmocm Business/Functional Technical	Identifies Resource needs and potential future gaps Backfill and backfill requests Contingencies >> plans for shifts in resource allocations Tracks resource statuses May be linked to Project estimations document for planning and forecasting OTL for tracking time spent on project		https://ucsdcollab.atlassian.net/wiki/spaces/SISCM/pages/395117658

ITS PPMO

Project Plans

Child Pages

Related content