Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MONTHLY Planning Comms (after planning week) #200

Closed
8 tasks
mxajPrice opened this issue Jul 8, 2022 · 2 comments
Closed
8 tasks

MONTHLY Planning Comms (after planning week) #200

mxajPrice opened this issue Jul 8, 2022 · 2 comments
Assignees
Labels
documentation Improvements or additions to documentation PBV: Product Management role: project management size: 1 pt 1 point = 6 hours or less

Comments

@mxajPrice
Copy link
Member

mxajPrice commented Jul 8, 2022

Overview

Every first week of the month the PMs and Leads have planning week. During this week, we do a retrospective of the previous month, look at whether progress is being made or has been made, and what the objectives of the next month are. After planning week, the PMs and leads have to communicate all the updates to the team.

This on-going issue will house the Action Items for each month.

Action Items

Blog

  • Create a copy of the PM Blog Template found here (right click on the file > Make a Copy > rename the file)
  • Draft the blog from notes on the last planning meeting MONTHLY Planning Week #155
  • Circulate to Leadership Team for input
  • Finalize and put a PDF version here in the drive
  • Link to PDF on the wiki here and list the topics under the link

Slack (when the blog is complete...)

  • Send a message to #access-the-data Slack channel with a link to the wiki and the bullet points from the blog

Team Meeting

  • Create agenda for the next Wednesday Team Meeting
  • Create slides for the meeting and put in the drive here

The first thing that needs to be done is to create a blog with all of the updates and monthly objectives. At the top of the blog there should be a bullet point summary and bullet point objectives. When the blog is finalized, a Slack message needs to go out with the link to the blog and the bullet points to #access-the-data. Then the objectives need to be incorporated into the following Wednesday Team Meeting along with any feedback needed from the team.

Resources/Instructions

@mxajPrice mxajPrice added documentation Improvements or additions to documentation role: project management size: 1 pt 1 point = 6 hours or less labels Jul 8, 2022
@mxajPrice mxajPrice self-assigned this Jul 8, 2022
@mxajPrice mxajPrice changed the title [Monthly] Planning Comms (after planning week) MONTHLY Planning Comms (after planning week) Jul 8, 2022
@mxajPrice
Copy link
Member Author

mxajPrice commented Jul 12, 2022

July 2022

Action Items

Blog

  • Create a copy of the PM Blog Template found here (right click on the file > Make a Copy > rename the file)
  • Draft the blog from notes on the last planning meeting MONTHLY Planning Week #155
  • Circulate to Leadership Team for input
  • Finalize and put a PDF version here in the drive
  • Link to PDF on the wiki here and list the topics under the link

Slack (when the blog is complete...)

  • Send a message to #access-the-data Slack channel with a link to the wiki and the bullet points from the blog

Team Meeting

  • Create agenda for the next Wednesday Team Meeting
  • Create slides for the meeting and put in the drive here

The first thing that needs to be done is to create a blog with all of the updates and monthly objectives. At the top of the blog there should be a bullet point summary and bullet point objectives. When the blog is finalized, a Slack message needs to go out with the link to the blog and the bullet points to #access-the-data. Then the objectives need to be incorporated into the following Wednesday Team Meeting along with any feedback needed from the team.

@mxajPrice
Copy link
Member Author

This is no longer a common recurring task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation PBV: Product Management role: project management size: 1 pt 1 point = 6 hours or less
Projects
Development

No branches or pull requests

2 participants