Additional process documents and forms will be added as they become available.

Policy

DocumentDescription
IT Project Management Governance and OversightDefines the governance structure, oversight requirements, and accountability standards for managing IT projects across North Carolina state agencies.

 

Process

DocumentDescription
Project Management ProcessDescribes the end-to-end project management methodology, lifecycle phases, and required controls for state IT projects.
Workflow Phases 
- Business ConceptProvides general guidance on due diligence activities involved with market and technical research, feasibility, stakeholder management, and budget and scope formulation. Document currently unavailable.
- InitiationOutlines activities required to formally establish a project, define objectives, and obtain authorization to proceed. Update forthcoming.
- Plan & ProcureProvides guidance for project related planning, solution design, procurement, acquisition of project resources, and making revisions. Update forthcoming.
- Build & ImplementDescribes processes for developing and testing project deliverables, and then deploying or transitioning them to production. Update forthcoming.
- CloseoutDefines the activities required to close a project in Phoenix and move it to complete. Update forthcoming.
Roles, Responsibilities & AuthoritiesIdentifies key project stakeholders and defines their responsibilities, decision-making authority, and governance roles. Update forthcoming.
Determining an IT ProjectProvides criteria for determining whether an initiative qualifies as an IT project subject to EPMO governance and oversight.

 

Decision Points

DocumentDescription
Business CaseGuidance on the Business Case decision point that is used to approve a project by either EPMO or the State CIO, indicating it is clear to expend funds. Document currently unavailable
Weekly StatusGuidance on the Weekly Status decision point for keeping the state informed about the status of a project. Document currently unavailable
Change RequestGuidance on the Change Request decision point to enter information required for an adjustment to a project’s scope, schedule, or budget. Document currently unavailable
Architecture ReviewGuidance on the Architecture Review decision point to understand what is required for Enterprise Architecture to approve a design for alignment with the state. Document currently unavailable
Security ReviewGuidance on the Security Review decision point to understand what is required for the Enterprise Security & Risk Management Office to approve a design for alignment with the State. Document currently unavailable
Go-Live Readiness

Defines an agency’s state of readiness and risk acceptance in determining whether a project is prepared for production deployment.

A Go-Live Readiness form is used to support this decision point.

Closeout
Guidance on the Closeout decision point to collect information required for approval to close a project and move it to complete. Document currently unavailable

 

Instruction

DocumentDescription
ScheduleGeneral descriptions on schedule management for a project, to include template related entries and modifications. Document currently unavailable
Budget

General descriptions on project budget formulation for a project, its maintenance, and what information is needed for the duration of the project lifecycle. Document currently unavailable

A Project Budget form is used to support budget formulation and maintain it over the lifecycle of the project.

Corrective Action

Instruction on drafting a supporting document to complement what has been offered in a Phoenix Weekly Status report when additional clarity is beneficial to stakeholders. Document currently unavailable

A Corrective Action form may be used to produce a more detailed plan for addressing adjustments to project deficiencies. 

 

Phoenix Project Management System Screens

DocumentDescription
Project InitiationProvides instructions for entering and managing project initiation information within the Phoenix system.
Executive SummaryExplains how to document and maintain high-level project information and status summaries in Phoenix.
Project Dates
Provides guidance for recording and updating key project milestones and schedule dates.
BenefitsDescribes how to capture and track projected and realized project benefits in Phoenix.
Budget/ActualsExplains the current approved and original project budget and the expenditure amounts from the financial system.
NCFSProvides guidance for managing North Carolina Financial System-related project information within Phoenix.
SAPProvides guidance for managing SAP system-related project information within Phoenix. Document currently unavailable
Assessment TypeExplains how to profile a project according to a self-assessed risk tool used to inform the Enterprise Security and Risk Management Office.
RiskProvides instructions for documenting, evaluating, and monitoring project risks.
IssuesDescribes how to record, manage, and resolve project issues affecting delivery.
DependencyExplains how to identify and track project dependencies that could impact success.
Contract, Security, & ArchitectureProvides guidance for associating contracts with a project and includes related security and architecture information for review.
Non-Compliance NotificationsDescribes information identified for correcting and managing project compliance.
Weekly StatusProvides instructions for entering recurring project status updates into the Phoenix system.
Decision Point History LogDescribes the record of actions made against all Decision Points for the project. Document currently unavailable
Change RequestProvides instructions for submitting project change requests within Phoenix.
DocumentsA SharePoint document repository exclusive to the project. Document currently unavailable
NotificationA record of system generated actions indicating what has been performed to support the project. Document currently unavailable
On This Page Jump Links
On