Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

Date

Attendees

Goals

  • PM Update

Discussion items

ItemWhoNotes
These sessionsKal / All 
  • Organization updates
  • PMCI / PPMO updates
  • Various program / project updates
  • Suggestions from all of you
Performance EvalsKal
  • Timeline
    • Self Evals have been submitted  
    • I'm evaluating  
    • SMT review  to  
    • Administering  to  
  • Questions?


Symptom checker / Take home equipmentKal

Symptom checker: https://blink.ucsd.edu/HR/services/covid-19/symptom-screening/

Take home equipment: Remote Work Norms & Guidelines

Slack Transition to TeamsAll

October 11 - Transition now

MS Team for Projects

Team: One for each project

Purpose: Keep project teams connected, informed, engaged and nurture a teamwork culture 

Audience: Project core team and stakeholders

Owner: PM / Core Team members

Member Management: PM and core team to add / remover members. Membership is open to all - including vendors. 

Channels:

  • General = general project chat. Anyone can drop in and discuss / ask questions regarding the project. Open channel. 
  • Core Team = Core project team chat. Private channel. 
  • Change Management = CLs, CPs, Lynn
  • Governance?

Constraints:

  • Project needs should not be at risk of being impacted by constraints:
    • limit of 200 channels per Team, including deleted channels
    • limit of 30 privatechannels per Team.
    • Private channels can have up to 250 members.
Project Portfolio Prioritization and PM assignmentsKal / Paul 

Meeting with the service owners to update the Project Records 

Meeting with the SMT next week for prioritization

Round Table / What is on your mind?All

Future Topic: Requirements / Design OTL & Templates

Kal
Future Topic: Atlassian Support / Atlassian Licensing KalFuture Topic: What is on your mind?

All



Action items

  •