Support/ProjectTemplate - Revision history

Kelimutu: updated per Q1 2022

2022-04-12T08:16:27Z

updated per Q1 2022

← Older revision		Revision as of 08:16, 12 April 2022
Line 1:		Line 1:
	This is a template for quarterly goals or projects you are leading. The purpose of it is ~~twofolded~~:		{{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.}}

	~~{{DRAFT~~}}

	=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 ~~/ Timeline~~'' section below if it's easier to follow.		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 ~~/ Timeline~~=		=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.

	~~The~~ project ~~plan could be something as simple as a bulleted list with action items~~, ~~owners, and deadlines:~~		=Result=
	* Initial kick-off meeting on July 27 w/ stakeholders ~~(David)~~		Describe the result of the project. Ideally, stakeholders should be able to update this when the project completed.
	* 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

	[[Category:Support ~~Archive~~]]		[[Category:Support]]

Kelimutu: category -> Support Archive

2021-07-14T09:12:03Z

category -> Support Archive

← Older revision		Revision as of 09:12, 14 July 2021
Line 40:		Line 40:
	* Present results at board meeting (David) on Aug 30		* Present results at board meeting (David) on Aug 30
	* Implementation of solution X (David & Michael) Sept 5		* Implementation of solution X (David & Michael) Sept 5

			[[Category:Support Archive]]

Djst at 08:58, 18 September 2012

2012-09-18T08:58:30Z

← Older revision		Revision as of 08:58, 18 September 2012
Line 23:		Line 23:
	=Scope=		=Scope=
	If necessary, provide info about what this goal is ''not'' about, or other relevant information that will help avoid confusion.		If necessary, provide info about what this goal is ''not'' about, or other relevant information that will help avoid confusion.

			=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 / Timeline'' section below if it's easier to follow.

	=Project plan / Timeline=		=Project plan / Timeline=

Djst: Created page with "This is a template for quarterly goals or projects you are leading. The purpose of it is twofolded: * To remove ambiguity about what exactly a project/goal is about, and what it'..."

2012-07-30T12:50:57Z

Created page with "This is a template for quarterly goals or projects you are leading. The purpose of it is twofolded: * To remove ambiguity about what exactly a project/goal is about, and what it'..."

New page

This is a template for quarterly goals or projects you are leading. The purpose of it is twofolded:
* 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.

This template can be used as a skeleton and simply copied to a new wiki page or etherpad.

{{DRAFT}}

=Title of project/goal=

Brief exec summary of the project's or goal's purpose. Also list who is owning it and any stakeholders.

=Problem statement=
Provide an accurate and clearly articulated problem statement:
* What is the problem that we are hoping to solve with this project?

=Desired outcome=
Describe with words the desired outcome after the completion of this project. What will be different? What will be improved? Be as clear and precise as possible, and avoid assumptions on what the reader's prior knowledge about it. In other words, elaborate on this more rather than less.

=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?

=Scope=
If necessary, provide info about what this goal is ''not'' about, or other relevant information that will help avoid confusion.

=Project plan / Timeline=
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.

The project plan should be a "living" part of the document and should be updated frequently to remain accurate. Again, it doesn't have to be super detailed, but it should contain enough info that you should be able to scan it and assess the overall status and health of 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.

The project plan 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