Project Management/Initiative FAQ: Difference between revisions

← Older edit

Project Management/Initiative FAQ (view source)

Revision as of 19:25, 16 December 2011

459 bytes added , 16 December 2011

→‎Why can't teams prioritize their projects now without having to implement a new process?

Malexis

Confirmed users

1,052

edits

@@ Line 1: / Line 1: @@
+== What is the goal of this initiative? ==
+The short-term goal is to bring visibility to projects that require assistance from teams like IT, Infrasec, Release Engineering, and QA to complete those tasks. These service-oriented teams are often asked to do more projects than what is possible with the resources they have available. The goal of this form is to allow the service-oriented teams to provide your project with the highest level of service.
 == How much time will it take me to complete the form? ==
@@ Line 33: / Line 37: @@
 == Why is this initiative asking about goals? ==
-For the past few quarters, [https://intranet.mozilla.org/2011Q4Goals#Strategic_goals organization-wide goals] is how we plan and ensure that Mozilla is healthy and relevant. Aggregated metrics on goals for submitted projects will help ensure that we have adequate resources to ensure your project is successful.
+For the past few quarters, [https://intranet.mozilla.org/2011Q4Goals#Strategic_goals organization-wide goals] are how we plan and ensure that Mozilla is healthy and relevant. Aggregated metrics on goals for submitted projects will help ensure that we have adequate resources to ensure your project is successful.
 == What if my projects don't align to the goals stated on the intake form ==
@@ Line 45: / Line 49: @@
 == Why can't teams prioritize their projects now without having to implement a new process? ==
-Teams are actively prioritizing their projects, but that is not the problem. There is a very high probability that any project that a given team is working on requires the assistance of at least one other teams to accomplish the project. There are certain teams (IT, QA, Security, Webdev, Operations, etc.) that are the most commonly requested to complete a project. When these teams ask all of the people who have requested them to do something to prioritize all of their requests, they all come back at priority ones. Every team feels that their projects are most important and if all projects are important, than no projects are important.
+Every team is actively prioritizing their own projects. However, there is a very high probability that these projects require the assistance of at least one other team to accomplish them. IT, QA, Security, Webdev, Operations, etc., are commonly requested to complete a project. These teams need to prioritize all the requests from across Mozilla and typically everyone's project is a P1. This is a way to prioritize at a higher level.
 == Who will manage the data captured on the project intake form? ==
@@ Line 57: / Line 61: @@
 == Does this integrate with any of our existing tools or platforms? ==
-* The project intake form is a short-term solution--it is not technically a tool and is not intended to integrate with or replace existing tools. In the future, we are investing in a simple overview tool that would allow this type of planning, but requirements have yet to be formalized.
+The project intake form is a short-term solution--it is not technically a tool and is not intended to integrate with or replace existing tools. In the future, we are investing in a simple overview tool that would allow this type of planning, but requirements have yet to be formalized.
 == Why can't we pilot this intake form with only the teams experiencing resource constraints? ==
-*While it's true teams with the most cross-functional dependencies and resource constraints will benefit the most from this initiative, having a comprehensive list is crucial to the success of all projects. Not submitting can lead to confusion and incorrect planning when those projects are eventually requested of the intended teams. Think of Mozilla as one big team, and while not every initiative will help every team directly, it will make us stronger as a whole.
+While it's true teams with the most cross-functional dependencies and resource constraints will benefit the most from this initiative, having a comprehensive list is crucial to the success of all projects. Not submitting can lead to confusion and incorrect planning when those projects are eventually requested of the intended teams. Think of Mozilla as one big team, and while not every initiative will help every team directly, it will make us stronger as a whole.
+== Will this information be published anywhere? ==
+After the data is sanitized and cleaned up, the team post the results on the Intranet. A link will be sent out to the company on where to find it in early January.
 == Where can I read more about this initiative? Who is on the team? ==
-* Read more about this initiative on the [[Project_Management/2011_Q4|2011 Q4]] page.
+Read more about this initiative on the [[Project_Management/2011_Q4|2011 Q4]] page.