900
edits
(category -> Support Archive) |
(updated per Q1 2022) |
||
Line 1: | Line 1: | ||
This is a template for quarterly goals or projects you are leading. The purpose of it is | {{SUMONavbar}}<br> | ||
{{admon/note|This is a template for quarterly goals or projects you are leading. The purpose of it is two folds: | |||
* To remove ambiguity about what exactly a project/goal is about, and what it's not about. | * To remove ambiguity about what exactly a project/goal is about, and what it's not about. | ||
* To make it easier for everyone to know the status of a project. | * To make it easier for everyone to know the status of a project. | ||
This template can be used as a skeleton and simply copied to a new wiki page or etherpad. | This template can be used as a skeleton and simply copied to a new wiki page or etherpad.}} | ||
=Title of project/goal= | =Title of project/goal= | ||
Line 20: | Line 20: | ||
=Success metric= | =Success metric= | ||
How will the success of the project be tracked? Which of the org's top goals does this project support? What KPI/needle are we trying to move? | How will the success of the project be tracked? Which of the org's top goals does this project support? What KPI/needle are we trying to move? | ||
=Stakeholders= | |||
Who are the stakeholders involved in this project? RASCI model can be used here. | |||
=Scope= | =Scope= | ||
Line 25: | Line 28: | ||
=Communication plan= | =Communication plan= | ||
At a high level, describe any communication plans (e.g. planned blog posts, forum thread posts, internal MoCo communication, etc) that should happen as part of this goal. Also specify who needs to do the communication -- you, community management, or someone else. This section can of course be merged with the ''Project plan | At a high level, describe any communication plans (e.g. planned blog posts, forum thread posts, internal MoCo communication, etc) that should happen as part of this goal. Also specify who needs to do the communication -- you, community management, or someone else. This section can of course be merged with the ''Project plan'' section below if it's easier to follow. | ||
=Timeline= | |||
The project timeline could be something as simple as a bulleted list with action items, owners, and deadlines: | |||
* Initial kick-off meeting on July 27 w/ stakeholders (David) | |||
* Delivery item #1 completed on week of Aug 13 (Rosana) | |||
* Delivery item #2 completed the week after item #1 (Cheng) | |||
* Present results at board meeting (David) on Aug 30 | |||
* Implementation of solution X (David & Michael) Sept 5 | |||
=Project plan | =Project plan= | ||
At a high level, describe what steps we need to take to get to the completion of this project. In some cases, it might be mostly unclear, in which at a bare minimum it should be clear what the next steps are. In other cases we may already have a pretty clear idea of all steps needed. | At a high level, describe what steps we need to take to get to the completion of this project. In some cases, it might be mostly unclear, in which at a bare minimum it should be clear what the next steps are. In other cases we may already have a pretty clear idea of all steps needed. | ||
Line 34: | Line 45: | ||
Remember that by writing a plan or next steps down, you also help yourself to get a better sense of the work to be done. Writing should not be seen as non-work or a waste of time, especially not if it also helps stakeholders and other interested parties to stay informed with the project. | Remember that by writing a plan or next steps down, you also help yourself to get a better sense of the work to be done. Writing should not be seen as non-work or a waste of time, especially not if it also helps stakeholders and other interested parties to stay informed with the project. | ||
=Result= | |||
Describe the result of the project. Ideally, stakeholders should be able to update this when the project completed. | |||
[[Category:Support | [[Category:Support]] |
edits