canmove, Confirmed users, Bureaucrats and Sysops emeriti
2,305
edits
Project Management/Initiative FAQ: Difference between revisions
Jump to navigation
Jump to search
Project Management/Initiative FAQ (view source)
Revision as of 17:45, 15 December 2011
, 15 December 2011no edit summary
No edit summary |
|||
| Line 34: | Line 34: | ||
* 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. | * 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. | ||
== 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"? == | |||
* 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 tool integrate with any of our existing tools or platforms? == | |||
* 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 just the teams that are having resource constraints? == | |||
While it is true that the teams that are most commonly requested to assist with projects will benefit the most from visibility into projects, it will only be beneficial to the organization if it is comprehensive. If there are major gaps in terms of Mozilla products that are submitted it will only lead to future confusion and incorrect planning when those projects are then formally requested of the intended teams. This confusion will negate the entire benefit of doing this initiative thus the only way to do it effectively is to do it comprehensively. 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. | |||