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

From MozillaWiki
Jump to navigation Jump to search
Line 2: Line 2:


==Crashkill==
==Crashkill==
* 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


==Electrolysis==
==Electrolysis==

Revision as of 20:30, 12 October 2011

Projects

Crashkill

Electrolysis

  • Provide management assistance running meetings
  • Identify 4Q goals for project and track short term goals to completion

Mobile

Performance

  • Create standards of legitimacy for responsiveness tests - clear methodology and configuration for running tests.
    • Startup path
    • Battery usage
    • Page load
    • Zooming
    • Panning
  • Create repeatable process for the above testing to benchmark.
  • Video stream capture for mobile devices set-up in engineering to get benchmarks.
  • A project plan to retrofit automated test harnesses to be Java compliant.

Java UI

  • Project plan and schedule for development.

Quality

  • Establish seed of quality program starting with performance

Silent Update

  • Manage effort running weekly meetings
  • Engage with Engagement, Product Management, releng, Security, and QA and keep them involved in the project
  • Kill major update pain points in 4Q

Telemetry

  • Work with engineering teams to identify and implement probes for top three Blizzard questions

Process

  • Help revamp the current meeting schedule (joint goal with Christian)

General Program Management

  • Develop initial template/tool for managing programs consistently
  • Elaborate program management related material (wiki) and continue to educate engineering teams about pm