User:KaiRo/Goals

Personal goals of KaiRo per quarter (in addition to ongoing routine work).

2015 Q1

[ON TRACK] Create a concept and prototype for a better topcrash metric that (de)prioritizes for more/less serious issues.
[ON TRACK] Familiarize with how the QE release process works.
[ON TRACK] Find how we can make the QE release process more effective and refine the release test plan wiki pages.

[DONE] Learn more about how QA train driving works and what can be improved in that process.
[ON TRACK] Help rest of the Firefox QA team figure out how to focus work better, figure out how we could get metrics on that.
[DONE] Attend TRIBE: AoS.

[MISSED] Get up metrics for OOM and GC crashes in addition to the overall rates, figure out possible additional groups to measure (GFX? JS? JIT?).
[DONE] Automate more ongoing Firefox QA metrics, get a first version of a dashboard up.
[DONE] Get verification process into a more uniform and transparent state (esp. in terms of bug queries). [Queries on dashboard are more visible now, new flag exists and is used, but we are de-emphasizing verification overall.]
[DONE] Connect more with people on the QA team.

[DONE] Figure out if and how we can get metrics for certain categories of crashes (OOM? JIT? GFX?) in addition to the overall rates.
[DONE] Determine if we'll do a stability work week in 2014, and if so, start organizing.
[ON TRACK] Get more into assembling metrics for desktop QA.
[AT RISK] Get verification process into a more uniform and transparent state (esp. in terms of bug queries).
[ON TRACK] Learn more about QA-driving desktop trains, potentially start leading one.
[DONE] Figure out if PM is still needed for FHR, keep track of ongoing initiatives.
[DONE] For personal growth, get at least subscribed to the first module of TRIBE.

[AT RISK] Figure out project management needs in QA and start working on them.
[DONE] Extend analysis on and blog about crash rate histories, possibly also take a look into graphing certain categories of crashes (OOM? JIT? GFX?).
[DONE] Make sure that Data Quality, Stability Probes and User Tips initiatives on FHR move forward.
[AT RISK] Get an initial round-up on who would need to be involved in a Firefox OS FHR-or-alike and where those people/groups stand in terms of opinions on it.
[ON TRACK] To extend PM knowledge, learn about how scrum and similar processes are being used at Mozilla and also how hiring processes work here.