Date
Attendees
Student Test - absent
Gerrity, Christopher (Deactivated) - absent
Lillian Maestas - absent
Discussion items
Time | Item | Who | Notes |
|---|---|---|---|
Share wins and cross functional project impacts and challenges | all |
| |
Smartsheet connectors | New connectors set up through service account, to avoid transition issues; will also show changes made by Smartsheet in Jira as the service account vs the personal user name Unfortunately no way to transition current connectors | ||
Kaltura and projects | Create project channel? Paul to invite Galen to next PMO mtg to discuss best practices Access, lifecycle / deprecation | ||
Project documentation | Based on the conversation and the need to meet the needs listed below, the answer was to create a “Shared Site” in SharePoint.
The shared site in SharePoint allows multiple people to be set-up as “owners”, which can be managed by the “owners”. Allows you to share folders, files, etc. if you need to only have people see certain content, etc. It also ties into a team that you can create on “Teams” for your project team (personally, I don’t like that feature, but I know some of our colleagues do). I am fairly sure that people on the team are already using Shared sites. One thing that also came up is that you have data/files on Google Drive, you can enter a ticket to help have it moved, as the Messaging and Collaboration team has scripts that they can run. | ||
Closed / done project - when they were done vs said they were done | |||
Closing projects! Should be Live | |||
Closing projects! Should be Done | |||
Capacity Planning |
| ||
What are you doing that's repeatable? | |||
Standard Project OTL | |||
Standard Events OTL | |||
Request: schedule mtg w/ your SO to review projects and their portfolio | |||
Reminder: project CoP | |||
New project set up (defaults)
| Standard process: when a new project is approved, create new
|