Confirmed users
1,052
edits
No edit summary |
|||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 37: | Line 37: | ||
== Why is this initiative asking about goals? == | == Why is this initiative asking about goals? == | ||
For the past few quarters, [https://intranet.mozilla.org/2011Q4Goals#Strategic_goals organization-wide goals] | 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 == | == What if my projects don't align to the goals stated on the intake form == | ||
| Line 49: | Line 49: | ||
== Why can't teams prioritize their projects now without having to implement a new process? == | == Why can't teams prioritize their projects now without having to implement a new process? == | ||
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? == | == Who will manage the data captured on the project intake form? == | ||
| Line 66: | Line 66: | ||
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? == | == 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. | ||