|
|
| Line 1: |
Line 1: |
| =Project Name=
| |
|
| |
|
| problem statement or why we do this project
| |
|
| |
| ==Goal==
| |
| Improvements to our search reporting
| |
|
| |
| ===Scope===
| |
| * Unified Telemetry to populate https://metrics.services.mozilla.com/search-dashboard/
| |
| * Ability to gather longitudinal history for new market Search test experiments
| |
| * Estimates for non UT population
| |
|
| |
| ==Duration==
| |
| * ASAP
| |
|
| |
| ==work breakdown and owners==
| |
| {| class="wikitable"
| |
| |-
| |
| ! Owner !! bug link !! status/notes
| |
| |-
| |
| | ? || [https://bugzilla.mozilla.org/show_bug.cgi?id=1257589 derived data stream canonical data set] || unassigned / blocker for project, has dependencies on client changes (!!)
| |
| |-
| |
| | ? || update search dashboard with UT data || ?
| |
| |-
| |
| | Example || [https://bugzilla.mozilla.org/show_bug.cgi?id=1259091 Desktop ADI and Search Query Volume Counts for Business Support] || Example
| |
| |-
| |
| | Example || Example || Example
| |
| |-
| |
| | Example || Example || Example
| |
| |-
| |
| | Example || Example || Example
| |
| |}
| |
|
| |
|
| |
| ===Minutes and Progress Reports ===
| |
| {| class="wikitable collapsible" style="width: 100%"
| |
| ! style="background-color: rgb(221, 221, 221);" colspan="2" | 2016
| |
| |-
| |
| |
| |
| * [https://docs.google.com/document/d/1oCfrnT_eOnleXyFmavf333UketRTOItBU9AU2hcVIIY/edit kick off meeting notes]
| |
| |}
| |
|
| |
| ==People==
| |
| list required competencies for people and, once defined, the people working on project. note that not all of these competencies will be required for every project
| |
| {| class="wikitable fullwidth-table"
| |
| | Project Champion ||
| |
| |-
| |
| | Program Management ||
| |
| |-
| |
| | Product ||
| |
| |-
| |
| | UX ||
| |
| |-
| |
| | Engineering || primary devs working on project
| |
| |-
| |
| | Other Engineering || subject matter experts contributing to project
| |
| |-
| |
| | Accessibility ||
| |
| |-
| |
| | Localization ||
| |
| |-
| |
| | Services ||
| |
| |-
| |
| | Incoming Bug Triage || this may be someone listed elsewhere, the key is to list people who handle triage
| |
| |-
| |
| | QA ||
| |
| |-
| |
| | Security ||
| |
| |-
| |
| | Privacy ||
| |
| |-
| |
| | Releng ||
| |
| |-
| |
| | Marketing ||
| |
| |-
| |
| | Legal ||
| |
| |-
| |
| |}
| |
|
| |
| ==Milestones/Iterations/Tasks==
| |
| high level milestones can be included in this page. more complex milestones and tracking information (typically bug lists) should be included on a milestone specific tracking page
| |
|
| |
| ==Dependencies==
| |
| feature, partner, resource, etc.
| |
|
| |
| ==Risks==
| |
| list risks in table below. assign a unique risk id to each risk. for ex., the project plan template may define risk ids prefixed with PPT like PPT001.
| |
| {| class="wikitable fullwidth-table"
| |
| ! Risk ID !! Description
| |
| |-
| |
| | PPT001 || Sample risk
| |
| |}
| |
|
| |
| ==References==
| |
| other references, very useful catch all category for existing links and text when cleaning up existing project pages
| |