Engagement/Integrated Marketing/Prioritizing: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
(Blanked the page)
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{ draft }}


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 [[Engagement/Integrated_Marketing/Definitions#Project_Brief|project briefs]] along with existing projects.
== Prioritization Process ==
# Engagement leads regularly review all recently approved project briefs and all [https://docs.google.com/a/mozilla.com/spreadsheets/d/1X5kUBkEAicEe2unDaaLGTYzAJbphWFoaJYBTasHrcHQ/edit#gid=1764494528 upcoming projects].
# Engagement leads consider the impact and complexity of the new projects relative relative to existing projects and document P1, P2, and P3 priorities.
# If priorities have shifted and project dates are impacted, project owners are notified and the project dashboard is updated.

Latest revision as of 21:16, 7 November 2017