Worked Well[edit]

Wikimania!
- good to have direct contact with users, concrete feedback led to implementation of useful features
- reminder that we have a huge community
Unstructured time provided really good opportunity to get to the bottom of some tricky bugs - also surfaced some semi-glaring omissions ahem gzip cough
^ good breathing room to learn/implement a lot of backend/CI stuff
ACTION!: Do we want to do this more frequently during the quarter? [Kristen]
Developers being suuuuuper responsive

Worked Poorly[edit]

Not being at Wikimania :( +1+1
Limn is painful +1000 (+1000000) +++++
- analytics is working on a db that will replace limn (may take a few quarters, per Moiz)
Sprint themes and velocity +1+
- eg title of Sprint 38 is "a lie"
- hard to find common theme between iOS and Android work when teams are not in sync with features and velcoity is different
- team thinks this is not a problem, sharing code is a boon
Sprint themes without sharing vision +1
- eg what are 4-5 themes to focus on to get editing #s up?
- need more prep for sprints with such important themes
- Howie wants Dan and Maryana to figure out time allocation for readers v. editors
- vision should be shared
Dan's time allocation to apps+1+1
- SUL stuff has been eating Dan's time
- *should* have time to participate in the usual PO responsibilites...actually shoudl be able to be ahead of things
- SUL off Dan's plate after this quarter
No idea of downloads / General Instrumentation
- iOS download numbers
- ACTION!: give Vibha & Moiz login access [Tomasz] Waiting on Design iTunes account [Vibha]
- ACTION!: give Vibha & Moiz access to data about user actions [Dan]
- ACTION!: monthly data review meeting [Dan/Vibha]
  - outcome should be deciding on basic 5-6 metrics that are consistent on an ongoing basis+1
Reaching Users
- reddit to recruit testers?
- test scripts/what do we want testers to test?
Insufficient testflight users +1 +1 +1 +1+1
- ACTION!: blog post and social media [Monte/Vibha/Moiz]
- ACTION!: paid testing services [Tomasz]
Tech Debt Sprint based on reviews and crash reports +1 +1+1+1
- ACTION!: this ties in to unstructured sprint idea above...make it so [Dan/Kristen]
- one sprint per quarter: unstructured/tech debt then crash reports
- Note: don't need to wait until a specific sprint to tackle tech debt
Trusting each other in the roles we have
- balancing speed with involvement
- cards for everything!

Confuses Us[edit]

Understanding Dev challenges for specific stories
Satisfactory Story breakdown so developers feel like they are ready to go
Ideas vs execution
analytics commitments to dashboards / sesion / page view data
- analytics team in general

Previous[edit]

Commitment to Page Styling vs increasing active editors +1+1+1+1++1 [DAN] with help Vibha & engineers
Unclear what schedule translation updates are happening at, and we only have yuvi with direct access in the system. Do we need more folks with access, or just a clearer schedule with Siebrand? ++1 (Yuvi will transition this to another team member (Siebrand wants only one person to have access in the team), volunteers welcome) [Bernd] volunteers.
A mediawiki page describing the app [DAN]++++