Program Management/Firefox/2011-Q4-Goals: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 13: Line 13:
==Cross Product==
==Cross Product==
===Crashkill===
===Crashkill===
* Socorro Q4 goals - features/bugs we would like to see implemented in Q4 to support the mandate of crashkill
* {{done|Socorro Q4 goals - features/bugs we would like to see implemented in Q4 to support the mandate of crashkill}}
** https://wiki.mozilla.org/CrashKill/Plan/Priorities#Q4.2F2011
** https://wiki.mozilla.org/CrashKill/Plan/Priorities#Q4.2F2011
* Dashboard for managing crash landscape - incoming crash rate, fixes crash rate, per component breakdown and release to release comparison.
* {{risk|Dashboard for managing crash landscape - incoming crash rate, fixes crash rate, per component breakdown and release to release comparison}}
* Triage process for handling new crash bugs logged.
** Blocked on metrics work.
* {{done|Triage process for handling new crash bugs logged}}
** Cleaned up subsets of bugs and have process for tracking incoming/outgoing.


===Telemetry===
===Telemetry===
Line 38: Line 40:


=Process=
=Process=
* Detailed analysis of how we use bugzilla within engineering - https://etherpad.mozilla.org/BugzillaInterviews.
* {{risk|Detailed analysis of how we use bugzilla within engineering - https://etherpad.mozilla.org/BugzillaInterviews}}
** Did pretty well with this but goal is now end of Jan 2012.
* Weekly, high functioning meeting where project managers and product managers get together and track the status and issues around features, programs and bugs - "Directly Responsible Individual" (DRI) meeting.
* Weekly, high functioning meeting where project managers and product managers get together and track the status and issues around features, programs and bugs - "Directly Responsible Individual" (DRI) meeting.
* Proposal for tracking triage of incoming bugs.
* Proposal for tracking triage of incoming bugs.
Confirmed users
2,492

edits

Navigation menu