Engagement/Integrated Marketing/Prioritizing

From MozillaWiki
Jump to navigation Jump to search
Draft-template-image.png THIS PAGE IS A WORKING DRAFT Pencil-emoji U270F-gray.png
The page may be difficult to navigate, and some information on its subject might be incomplete and/or evolving rapidly.
If you have any questions or ideas, please add them as a new topic on the discussion page.

Prioritization is a process by which a team decides what projects they will be working on in the near future and their relative impact.

For the best outcome, prioritization should be more scientific and less subjective. Most Engagement teams now prioritize projects within their own team based off of the requirements and criticality of the request, which is great, but it doesn't help cross-functional projects and people who support multiple teams. Since most of our major projects are cross-functional by nature, how do we (as an Engagement team) decide what should be worked on in the near future?

We are currently developing a pragmatic and transparent approach to prioritization, but in the short-term, the Engagement leads will review all new major project briefs along with existing projects.

Prioritization Process

  1. Engagement leads regularly review all new project(s) with a status of "Awaiting Approval".
  2. Engagement leads review previously approved list of active projects.
  3. Engagement leads consider the impact of new projects and other projects previously approved and consider priorities.
  4. Engagement leads approve/reject the new project(s).

If a newly approved project will directly impact the launch of existing active project, Engagement leads contact the accountable person on the existing active project to determine next steps. If a new project is approved, the status column in the project dashboard should be changed to "Active".