Created
January 19, 2017 23:57
-
-
Save hollyallen/6ed951d3f4de0ff6ffb81e3f559cb67f to your computer and use it in GitHub Desktop.
A very complete weekly project update email template
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
To: <email list set up only for sending these updates to> | |
Subject: <Project Name> Project Status - <today's date> | |
Change Summary for the week | |
* bullet points, not too many | |
* Finished items, decisions, actions taken | |
* Not things like "still working on that thing from last week" | |
Overall Strategy and Summary | |
* One bullet summary of the goals of the program | |
* Strategy to reaching those goals | |
* Should tie to actions this week and milestones below | |
* Good info for folks who have just been forwarded this week's update and know nothing little your program | |
Milestones | |
* <Milestone date> - <Milestone status> | |
** Short description of this milestone ("whiz bang feature live for users") | |
** Any decisions made, could be this week or further back, depends on how disruptive | |
** Goals | |
** Risks | |
** Mitigations | |
Overall Risks and Mitigations | |
* Every program has risks | |
* How are you mitigating them? | |
Assumptions | |
* Overall program assumptions | |
* Like staff size and budget | |
* Maybe availablity of other departments |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thanks for posting! FWIW, nowadays I'm much more into posting KPIs in lieu of text. A Jira burndown is worth a thousand words. :) So I basically have
Hmm, somewhere I lost track of Risks and Mitigations and Assumptions. That's probably bad.