Wikimedia Apps/imported/Retrospective-April 30 2015

= Previous Retrospective Actions =
 * Action! split our team norm page from mobile web team norm page [KL] DONE
 * Action! Revise first team norm to say something like: "If it isn't documented, it didn't happen" in order to separate concerns of documentation from communication (ensure both happen) DONE
 * Action! socialize and document new team norm (or add this information to existing appropriate team norm): "More ad hoc hangouts in the bat cave" DONE
 * Action! Can we get Vibha on IRC consistently? DONE
 * Action! Show the rest of design IRC Cloud (mayeb they're already on it?) [Monte]


 * Action! draft suggestions for reforming Quarterly planning and share with team [KL] NOT DONE
 * Action! email to mobile-tech on remote conversation protocols [BG] DONE, ONGOING
 * Action! write up a GitHub proposal for the team (process handed off to BG) [AB] ONGOING, DONE
 * BG talking to Greg/Yuvi, other stakeholders
 * Action! send email to kickoff conversation about iOS release progress: how do we communicate better? [BG] DONE
 * still come documentation to clean up, but tracked on process board

= Worked Well = - Onboarding checklist - People helping out in IRC / Hangouts - MOAR Android devs - Android production release was painless (ok, was mostly bugfixes anyways) - Good API bugs discovered by TSG testing - Ready for Design signoff column -Once got going, iOS fixes for prod release - Ready for QA column + elena has been great!So great! -Appsen stepping up to make post re-org structure better suited to needs - Prototyping new features - HockeyApp crash reports - Standups are getting shorter… but could get just a little more succinct - Devs "shepherding" cards to "Done" - WebView time to change is minimal

= Worked Poorly = - Lots of ambiguity over WMF account setup - Re-org was clumsy in some regards, ie cutting the head off the apps team : - Less iOS Devs - Tomasz+Dan+Moiz leaving :( - Handled iOS release process poorly (but we are also already working to fix this) - Implementation of feature card process before developer acceptance - No analytics on crash rate or people whose migratiosn are failing++ - Attempts to improve CI & dev workflow (unclear process, hard to make decisions, lack of autonomy, unclear if/how/when we'll get support) +++ - (from monte)  Why can't release engineering own apps release engineering? Can we get resources for this? - Still have double Android iOS meetings (like this one!)+++ - Build automation - some loose ends that truely make this hands off+ - QA not reproducing critical bugs +++
 * loss of wikipedian perspective? (lean on community liason, Reading community researcher, Village Pump, outreach) ++
 * agreed, at least we aren't working on editing flows atm
 * Also need ot me inclusive of web
 * especially now that we're at this size

= Confuses Us = - Prototyping the same thing on iOS and Android simultaneously...?+++ - Canihaz monthly health check with mean/median/stdev scores - Design review process - iOS release process. lots of moving parts and manual intervention across many "lanes" - Confidence in patch submission for huge landscape of device configurations ++++ - (automated testing FTW, from corey) - A couple of the cards were a little ambiguous what they're asking for (Chinese card)
 * what are the right intervention pointsto engage design?
 * design changes right after merge

WINNING - Confidence in patch submission for huge landscape of device configurations ++++ - (automated testing FTW, from corey) Action! Clarify what devices/configurations are supported in Android/startegies fro support, deprecation [Stephen]
 * starting CI/automated testing convo on Android side
 * understandign device support
 * CI in general
 * haven't been able to get support from RelEng/CI
 * Keep pushing on existing tickets that Bernd has filed (one of the two is actually from Yuvi)

- Attempts to improve CI & dev workflow (unclear process, hard to make decisions, lack of autonomy, unclear if/how/when we'll get support) +++ Action! Write user stories to clarify requirements - QA not reproducing critical bugs +++

- Still have double Android iOS meetings (like this one!)+++

- Prototyping the same thing on iOS and Android simultaneously...?+++