Confirmed users
1,052
edits
Project Management/Initiative FAQ: Difference between revisions
Project Management/Initiative FAQ (view source)
Revision as of 19:25, 16 December 2011
, 16 December 2011→Why can't teams prioritize their projects now without having to implement a new process?
| (12 intermediate revisions by 3 users not shown) | |||
| 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? == | == How much time will it take me to complete the form? == | ||
| Line 33: | 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] 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 41: | Line 45: | ||
== What happens if I don't submit my projects? == | == What happens if I don't submit my projects? == | ||
Not submitting could hinder your projects' chances for success and put others at risk. When the larger group doesn't know what your team is working on there's less potential for collaboration and dependencies can go unidentified. We can do this! | |||
== 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? == | ||
The [[Project_Management/2011_Q4#Team|project management initiative team]] will be initially reviewing, cleaning up, and communicating to the entire organization on the submitted projects. Prioritization and next steps will be determined by the same Directors and team leads who submitted the projects along with guidance from the steering committee. The main goal during this first phase of the initiative is just to bring visibility to all of our projects, but not directly affect how they are managed. | |||
== What is the outcome of "announcing final priorities"? == | == What is the outcome of "announcing final priorities"? == | ||
During this first phase of the initiative, little will change in terms of priorities and the projects themselves. This short-term solution is only to bring visibility and to allow specific teams to have a better view of what is going to be requested of their teams for short-term planning. The Directors, executive management, and the steering committee already do quarterly planning, which directs the types of projects we are all working on now. This short-term solution will only be used to augment high level planning and to assist the organization with being able to meet the needs of requested projects. | |||
== Does this integrate with any of our existing tools or platforms? == | == 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. | |||
== Why can't we pilot this intake form with only the teams experiencing resource constraints? == | == 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. | |||
== 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. | |||