Program Management/search reporting
Jump to navigation
Jump to search
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
Owner | bug link | status/notes |
---|---|---|
? | derived data stream canonical data set | unassigned / blocker for project, has dependencies on client changes (!!) |
? | update search dashboard with UT data | ? |
Example | Desktop ADI and Search Query Volume Counts for Business Support | Example |
Example | Example | Example |
Example | Example | Example |
Example | Example | Example |
Minutes and Progress Reports
2012 | |
---|---|
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
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.
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