Program-Project Management Framework

The Program-Project Management Framework provides a consistent approach to managing projects across Systemwide Procurement through standardized intake, project classification, templates, file management, and portfolio visibility. Whether you're starting a new project, participating on a project team, or seeking portfolio visibility, this site provides the resources and guidance you need.

Quick Links

Get Started

Learn where to begin whether you're starting a new project or transitioning an existing one.

Download Templates

Access the standard, required templates used to manage projects.

Explore Framework Terms

Reference key definitions and framework terminology.

Understand File Management & Structure

Learn how project files should be organized and shared.

Shared Language & Definitions

Establishes common terminology, definitions, and structure for shared understanding across teams.

Operating Structure

Defines how projects are organized and managed, including hierarchy, tiering, and roles.

Intake & Portfolio Visibility

Provides a phased approach to intake to boost visibility primarily, with consideration to future state prioritization.

Standard Templates

Delivers consistent templates to support project management, scaled to the project.

File Management

Introduces a standardized Box folder structure and file management approach to boost collaboration and consistency.

Tooling

Aligns process framework with enabling technology for tracking and reporting.

Communications & Collaboration

Establishes a model for project communication, stakeholder engagement, and collaboration.

Frequently Asked Questions

The PM Framework provides a common approach for organizing, managing, and delivering project work across SWP. It establishes shared processes, templates, file management, terminology, governance, and tools to improve consistency, visibility, and project outcomes.

The July 1st launch applies to Capability Delivery projects within STO, IAS, EDP, and Travel. These projects typically delivery systems, processes, tools, policies, organizational changes, or other capabilities to support strategic priorities. Refer to the Glossary of Terms for more information and definitions.

Not yet. The July 1st launch focuses on Capability Delivery projects within STO, IAS, EDP, and Travel. Project management processes for SaVE team projects will be introduced as part of a future rollout planned for 2026. Additional guidance and support will be provided prior to implementation. 

The PM Framework is intended to support project work moving forward, not create unnecessary administrative work. For projects already underway:

  • Submit the project through intake so we have a record of all active projects.
  • You do not need to recreate project documentation that has already been created. New project deliverables and activities should adopt framework templates where practical (e.g. open projects should leverage the project closeout template).
  • You do not need to recreate existing project folders into the standard Box structure. However, you may do so if beneficial for visibility, collaboration, or long-term record retention.

A project is a temporary, structured effort undertaken to deliver a defined outcome, capability, or change that is new or significantly different from ongoing operations. For more details, refer to the Glossary of Terms.

Yes, all Capability Delivery projects within STO, IAS, EDP, and Travel should be managed through the PM Framework. Guidance for SaVE team projects will be introduced during a future rollout planned for Fall 2026.

Ongoing operational activities, recurring work, and routine business processes are not managed through the PM Framework. Refer to the Glossary of Terms for more information.

Project intake provides visibility across SWP, supports coordination between teams, and helps apply consistent project sizing and reporting. It also helps leadership understand the breadth of work occurring across the organization.

No. As of now, intake is used for visibility and project sizing only. It is not a project approval process and does not prevent teams from initiating work.

Projects are assigned a tier based on factors such as complexity, risk, impact, and stakeholder involvement. Tiers help determine the appropriate documentation, governance, reporting, and oversight for a project. Refer to the Operating Structure Overview Guide for more information.

Yes. Projects should use the standard templates and Box folder structure to support consistency, collaboration, knowledge sharing, and visibility across SWP.

STO provides consultation, resources, office hours, project intake support, and ongoing guidance to help teams successfully apply the framework and delivery projects. Please reach out to Christina Jones for more information.

Stay in the loop!

Subscribe to our email updates and never miss the latest news and exclusive offers!

Select your subscription