Mobile/QuarterlyReview

Mobile quarterly review

The following is based on the framework that E3 used to structure their quarterly review (slide deck here: https://meta.wikimedia.org/wiki/File:E3-QuarterlyReview-Jan2013.pdf, with some modifications based on lessons learned from that meeting.

Let's flip through E3's presentation quickly and see if this structure makes sense for us, or if we need to add/remove/change anything.


 * 1) Team intro and Annual Plan goals [Tomasz]
 * 2) who are we?
 * 3) what are our targets for this fiscal year?
 * 4) Recap of Q2 (Oct.-Dec.) [Arthur]
 * 5) Goals
 * 6) which of our annual goals/targets did we choose to focus on in this quarter and why?
 * 7) Features roadmap
 * 8) what did we deliver to users each month?
 * 9) Impact
 * 10) what was the impact of these features on the Wikimedia ecosystem?
 * 11) did we meet our goal for the quarter? why/why not?
 * 12) Plan of action for Q3 [Maryana]
 * 13) Goals
 * 14) which of our annual goals/targets did we choose to focus on this quarter and why?
 * 15) Features roadmap
 * 16) what do we plan to release this quarter?
 * 17) Intended impact
 * 18) what is the intended impact on the Wikimedia ecosystem?
 * 19) are we on target to meet our goal for the quarter? why/why not?
 * 20) Successes
 * 21) highlight our biggest successes in Q2
 * 22) Challenges
 * 23) highlight our biggest challenges in Q2
 * 24) Asks
 * 25) do we have what we need to meet our goals for Q3?
 * 26) what resources do we need to help us meet those goals?
 * 27) Video tech at the office is moving at a glacial pace
 * 28) Dedicated operations support
 * 29) Buisness analyst
 * 30) Better recruiting
 * 31) Better testing env. Espeically for performance testing

--- Notes:
 * Should we focus more on Q2 or Q3?
 * If we need to cover Q4... team's not doing Q4 planning until AFTER this review mtg [Tomasz]
 * Do we really need the entire team here? [Tomasz]