This is a work in progress for the Marketing Project Management Simplification project.
Marketing uses GitLab for agile project management including groups, projects, epics, roadmaps, issues, labels, and boards. Read through the documentation on each of these GitLab features if you are unfamiliar.
Marketing Departments collaborate to produce Integrated Campaigns. An Integrated Campaign is a communication effort that includes several campaign tactics such as blog posts, emails, events, advertisements, content on about.gitlab.com, videos, case studies, whitepapers, surveys, social outreach, and webcasts. An Integrated Campaign will have a campaign theme that summarizes the message we are communicating to our market.
Have a new campaign idea? Make a suggestion
We cultivate a deep understanding of our own product by using GitLab to manage our planning, collaboration, and execution of Marketing activities.
The latest Project Management recommendations can be found here from FY21-Q2 Agility Project
The latest recommendations for Milestones from FY21-Q2 Agility Project
Within the www-gitlab-com repo (parent repo to Marketing) there are weekly milestones, which some teams use plan a weekly sprint cadence. Each of these sprints begins with "Fri:**" for the Friday upon which that sprint ends, making them searchable in a list here.
Each week on Monday, any open MRs and issues still assigned to the previous week's milestone are bulk moved forward to the next week, and the previous milestone is closed out. This is a manual process currently performed by Danielle.
The latest recommendations for Groups and Projects from FY21-Q2 Agility Project
CMOlabel. (Don't apply the CMO label to other epics.)
mktg-status::and one of four statuses. Status labels should be used on all issues within the Marketing group:
mktg-status::plan- work that is proposed, in an exploratory state.
mktg-status::wipand creating an merge request (MR), if appropriate. The plan status is optional, as issues that don't require formal planning can be opened and labeled
mktg-status::wip- work in progress that has been accepted and assigned to a DRI.
WIP:. At GitLab we allow reviewers to start reviewing right away before work is complete.
WIP:should be removed from the title.
mktg-status::review- work has been completed enough that it is ready for formal review and approval.
mktg-status::scheduled- work that is complete but should be scheduled for a future date.
closed- when work is delivered the issue should be closed.
Each Department within Marketing can have "additive" labels - meaning they are used to enhance the tracking and workflows for that respective team. These "additive" labels are used in conjunction with the broader Marketing labels. The Department label usage is documented on each of the respective handbook pages:
When a new issue is opened in any project, the issue description will contain a small snippet of text applying that teams' label & Marketing scoped
Apply Templateand continue as normal
The default text is minimal and generic. Any team can make the collective decision to update the text. Access to modify the text may be limited based on group/project permission level, if you do not have access to the
General settings section, please reach out to
@mktg-ops via slack.
Please note this is not an issue bot there is no dynamic functionality. The default issue text applies to all issues opened within that project and the text should be broad enough to encompass a roles within that team.
Expandnext to Default Issue Template
mktg-status::planlabel in that section
Save changes. The changes be applied immediately to any new issue opened.
If you have any issues &/or questions, please reach out to the MktgOps team (
@mktg-ops) via slack.
Figuring out how where and how to create a board, epic, label can be confusing. The following diagram is a very high level example of how it all fits together. If there are questions please ask in the #mktgops slack channel (*must be GitLab team member for active link).