Team Practices Group/Q2 2014 mobile web health check

Comments from 2014-10-03 Mobile web health check survey. Survey spreadsheet here: https://docs.google.com/a/wikimedia.org/spreadsheets/d/1diG8Yc80aGibhIp9Lce3w8Pk4xMHM9N6Bq31KojYZSk/edit#gid=0

Releasing: Crappy

We do a lot of lightning deploys; we break stuff with new deploys. Browser tests coud use love, they miss things. Could use QA peeps. 

Process: Awesome

Can give eg Florian stories, Kaity thinks internal processe are THE BEST AT WIKIMEDIA!!! It's obvious how to plugin to our development process; it's easy to work remotely because there is good structure and people are easy to communicate with. Could do some fine tuning on third-party stuff. When Zero needs stuff from us they are very pleased at the way we deliver. We overperfom.  

Code quality: Awesome

Baha: it's not documented but it's awesome; we've cleaned up a bunch in the past month; lots of improvement for e.g. watchlist. Not a lot of cruft. Small scope helps. Jon has some reservations calling it awesome. 

Value: Awesome

We get tweets, people think mobile wikipedia is cool; billions of PEOPLE LIKE US!!!!!!! Editing at a higher rate than desktop; see Victor's video :-) 

Speed: meh

VE slog, wikigrok stuff has been slower than anticipated, stuff falls off the plate...we could be doing more, faster.  

Mission: meh

We know why we're here but we should be reminded of it; more user testing outside of SF. VE work didn't feel mission-driven. Kaity: feels like there was mission but we didn't talk about it. Occasionally we fall in to missionless holes. Could stand to focus on en-wp less...We're doing a good job with the limited resources we have. Could do a better job coordinating with language engineering, more for people with slow connections. Our awareness indicates that we're mission aligned, but we are resource constrained. Feel like we have better morale and better focus than six months ago. Planning is a concern; being proactive v reactive. Would be good to look long-term again. Let's resuscitate our mission! Kaity is depressed that we didn't pick awesome.  

Fun: Awesome

Baha will soon find out exactly how fun.  

Learning: meh

Our team getting bigger might help (or does it!??!?); so much to do no time. Jon feels 'crappy'. 

Support: crappy

We are always waiting. We get blocked when it's stuff we need from other teams. Acknowledge that it's not always easy to give support.  

Destiny: meh

Sometimes we get pulled into things that we don't think are important to work on (VE); but we can do radical things and get away with it. Sometimes we get pushback and have to justify it. Community is a factor (eg infoboxes). We can voice our opinions compared to other teams. Meh on upward trajectory. During selfiepocalypse we could call some shots.  

Open-source citizenry: meh

Workaround has been to avoid third party software :-/ We upstream bugs, occasionaly contribute patches, just not as active as we shoudl be; wikidata will be an interesting indicator. We're responsive to bugs that are filed. Florian is fairly active contributor, we review patches. We could better leverage existing open source software and libraries. Jon says crappy.