Confirmed users
141
edits
Marketing Collective/Structure: Difference between revisions
no edit summary
No edit summary |
|||
| (8 intermediate revisions by one other user not shown) | |||
| Line 18: | Line 18: | ||
* <b>Product Marketing</b>: adapt product and brand messaging locally, support and promote product releases, imagine new campaign concepts for your country and build user community around our products. | * <b>Product Marketing</b>: adapt product and brand messaging locally, support and promote product releases, imagine new campaign concepts for your country and build user community around our products. | ||
Contributors are free to choose modules they want to participate in. Once they have selected the ones they are interested in during the signup process, they are introduced to the appropriate Module Owners. Depending on the contributor's experience, Module owners may provide them with extra training and/or educational material to help get them up to speed. | |||
Modules will also be prioritized against each other so that locales with less contributors can participate in the most important activities. | |||
</div> | </div> | ||
| Line 25: | Line 28: | ||
The Marketing Collective schedule is comprised of different types of activities, categorized by nature and recurrence: | The Marketing Collective schedule is comprised of different types of activities, categorized by nature and recurrence: | ||
* <b>Recurring Tasks</b>: these tasks need to be performed regularly (usually weekly or monthly) | * <b>Recurring Tasks</b>: these tasks need to be performed regularly (usually weekly or monthly) as part of the modules contributors are joining. They can be assigned to specific contributors who are responsible for them, or be shared among several members. They can also depend on countries and needs. Example: localization of our monthly Newsletter, flagging new campaign launched by competitors | ||
* <b>Special Assignments</b>: unique tasks that only need to be performed once. These tasks will be part of "weekly sprints" and usually be more time-sensitive and temporary priorities. Examples: event planning, release promotion, campaign promotion, product messaging adjustments. | * <b>Special Assignments</b>: unique tasks that only need to be performed once. These tasks will be part of "weekly sprints" and usually be more time-sensitive and temporary priorities. Examples: event planning, release promotion, campaign promotion, product messaging adjustments. | ||
</div> | </div> | ||
<div style="display:block;-moz-border-radius:10px;background-color:#d1dffa;padding:20px;margin-top:20px;"> | <div style="display:block;-moz-border-radius:10px;background-color:#d1dffa;padding:20px;margin-top:20px;"> | ||
===Schedule and Planning=== | ===Schedule and Planning=== | ||
We are using a sprint-based approach inspired by the SCRUM methodology in order to plan, coordinate and track progress: | We are using a sprint-based approach inspired by the SCRUM methodology and use work sprints in order to plan, coordinate and track our progress. | ||
Sprints: The sprints are bi-weekly periods around which activities are planned and performed | |||
* <b>Sprints</b>: bi-weekly periods around which activities are planned and performed. Ahead of a sprint, all proposed activities get submitted and prioritized against each other by Module Owners. Contributors and Regional leads can of course submit activities too. | |||
* <b> | * <b>Sprint updates</b>: an email update will be sent to the entire group at the beginning of each new sprint. It will contain: | ||
* | ** Various engagement updates on our products, projects and the organization to make sure everyone is equally informed of what is relevant to our marketing efforts | ||
** Reports from each Modules Owner on progress made during past sprint(s) | |||
** Special assignment(s) to mark temporary / timely priorities (they can submitted by anyone and will be prioritized by Modules Owners) | |||
</div> | </div> | ||
<div style="display:block;-moz-border-radius:10px;background-color:# | <div style="display:block;-moz-border-radius:10px;background-color:#d1dffa;padding:20px;margin-top:20px;"> | ||
==Roles== | |||
===Roles=== | |||
There is a number of different stakeholders in the Marketing Collective program. They can be classified according to their responsibilities and involvement: | There is a number of different stakeholders in the Marketing Collective program. They can be classified according to their responsibilities and involvement: | ||
| Line 50: | Line 61: | ||
*<b>Regional Lead</b>: a regional lead represents all members of the Marketing Collective in a given region at meetings, calls and summits where attendance is limited. The can also advise contributors and mentors in their region. | *<b>Regional Lead</b>: a regional lead represents all members of the Marketing Collective in a given region at meetings, calls and summits where attendance is limited. The can also advise contributors and mentors in their region. | ||
*<b>Module Owner</b>: a Mozilla employee with expertise | *<b>Module Owner</b>: a Mozilla employee with expertise in a given functional area. The Module Owner submits Recurring Tasks and Special Assignments - sorted by workload and urgency - to be performed by volunteers during a sprint. Module Owners work together with the Program Lead to prioritize the Sprint To-Do List and provide volunteers with training, directions and assistance over the course of the sprint. | ||
</div> | </div> | ||