Confirmed users
1,052
edits
| Line 47: | Line 47: | ||
* Due to the project intake-form to be only a short-term solution and just a basic Google Doc form, it is not technically a tool. We are not implementing a tool at this time as the first phase of the this initiative is to just bring visibility and not make anything more complicated. In the future, we are investing a simple overview tool that would allow this type of planning, but requirements have yet to be formalized. | * Due to the project intake-form to be only a short-term solution and just a basic Google Doc form, it is not technically a tool. We are not implementing a tool at this time as the first phase of the this initiative is to just bring visibility and not make anything more complicated. In the future, we are investing 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 | == Why can't we pilot this intake form with only the teams experiencing resource constraints? == | ||
While it | 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. | ||
== 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. | ||