canmove, Confirmed users, Bureaucrats and Sysops emeriti
2,305
edits
m (→Overview) |
|||
Line 1: | Line 1: | ||
== Overview == | == Overview == | ||
The Webdev [[Webdev/Web_Production|Web Productions Teams]] was formalized in 2011 to help drive technical projects from ideation to completion and ensure projects are as successful as possible. The [[Webdev/Web_Production/Positions/Web_Product_Engineer|Web Product Engineer]] (WPE) role was created as the technical project manager (TPM) on new Webdev projects. Almost all of these new projects required coordination of the engagement, webdev, QA, infrasec, and IT groups. The creation of the WebProd team has been a success, but it also exposed a number of issues that got worse as the company was rapidly growing. The number of projects initiated were increasing and it became impossible to launch everything requested given the resource constraints in all the groups required for any given project. Once WebProd realized that not everything was possible they set out to develop a method to get priorities documented for all projects. This was a difficult task because each group requesting projects could prioritize their own projects, but they would not have visibility into other groups. The cross-group and Mozilla-wide visibility into everyone's projects leads to groups like IT, InfraSec, and QA to be over utilized and unable to commit to all of their requests. | The Webdev [[Webdev/Web_Production|Web Productions Teams]] was formalized in 2011 to help drive technical projects from ideation to completion and ensure projects are as successful as possible. The [[Webdev/Web_Production/Positions/Web_Product_Engineer|Web Product Engineer]] (WPE) role was created as the technical project manager (TPM) on new Webdev projects. Almost all of these new projects required coordination of the engagement, webdev, QA, infrasec, and IT groups. The creation of the WebProd team has been a success, but it also exposed a number of issues that got worse as the company was rapidly growing. The number of projects initiated were increasing and it became impossible to launch everything requested given the resource constraints in all the groups required for any given project. Once WebProd realized that not everything was possible, they set out to develop a method to get priorities documented for all projects. This was a difficult task because each group requesting projects could prioritize their own projects, but they would not have visibility into other groups. The cross-group and Mozilla-wide visibility into everyone's projects leads to groups like IT, InfraSec, and QA to be over utilized and unable to commit to all of their requests. | ||
'''Probing question: How would groups like IT, QA, or InfraSec know what projects are priorities given most of Mozilla needs their services to launch a product and none of the project requesters know everything that IT, QA, and InfraSec are being asked to do?''' | '''Probing question: How would groups like IT, QA, or InfraSec know what projects are priorities given most of Mozilla needs their services to launch a product and none of the project requesters know everything that IT, QA, and InfraSec are being asked to do?''' |