Wikimedia Apps/Team/Retrospectives/2015-11-06

ANDROIDEdit

November 6, 2015

Previous Retrospective ActionsEdit

  • Action! Let's remember to estimate things
    • Use standup for notifying of estimation needs, adhoc hatjitsu
  • Action! Column to backlog: Design Doing (no more questions for design that aren't in the sprint) [MAX] DONE
  • Action! Need more sync up/communication w/Reading Web team ("MFE styles break our presentation") [EMAIL, MAX] ONGOING, NEW ACTION BELOW
  • ORDERED Action! Need update on ordered testing devices [ADAM] WAITING ON SAMSUNG DEVICE

Worked WellEdit

  • We officially got a Kaity!+++
  • Approved by Google for Play Store featuring (against all odds) +++
  • CPU load fix seems to be working++
  • knowing how much our app actually crashes -- and why!++
  • flaky tests getting fixed!
    • just a timeout -- good old occam's/ockham's razor strikes again+
  • Team discussion of testing generally+
  • Being able to contribute fix and feature code to server side (devs aren't app locked)++
  • Volunteer contributors keep contributing.+
  • More focus on improving our test coverage and quality

Worked PoorlyEdit

  • Bottlenecks in the workflow again
    • Flaky tests
    • Slow code reviews
  • Most tasks getting done are zero points (hopefully not just unestimated).
    • Not a problem, necessarily, but messes with velocity.
  • More surprises from Parsoid output (main pages, red links)
  • Crashes on a nontrivial subset of devices (no fault of our own)
  • We haven't spent a lot of time celebrating wins (retro included)

Confuses UsEdit

  • Plan for grooming, triage, design review/sync
    • iOS model?
  • Future of link preview
    • Why do we need another link preview A/B test?
  • How reading strategy will effect android team
  • Test timing on CI
  • Hyper aggressive MediaPlayer API
  • ProGuard+
  • GSOC/Outreachy -- how many can we accommodate?

Top three items, from "Worked Poorly" and "Confuses Us" (if short on time)Edit

Action ItemsEdit

  • ORDERED Update on Samsung devices? [ADAM] [DONE PINGED]
  • Add cards for detecting regressions when pulling in CSS changes from the MW extension [Stephen]
  • Investigate moving emulator-dependent tests to async operation [Dmitry]
  • DONE, ORDERED Adam ping Toby about crashes on nontrivial subset of devices [ADAM]
  • Weekly digest of funny/positive Play Store feedback [Dmitry]
    • "Stars from Midnight"
    • "The Midnight Copy"
  • Cancel design review [MAX] DONE
    • Standups/adhoc meetings instead
  • Email thread: How reading strategy will effect android team [KAITY]
  • Email thread: GSOC/Outreachy -- how many can we accommodate? [MICHAEL]


iOSEdit

November 10, 2015


Previous Retrospective ActionsEdit

  • Action! Gut check on assets managment in pholio, Kaity to use pholio more DONE
  • Action! IRC norms for Phab communication: Email thread [BRIAN] DONE NOWish
  • Action! Get more regular updates w/design (standups?) [MAX EMAIL THREAD CONT'D]
    • Or post-estimation kick-off?
    • If no decision made after a few days of the email thread, let's just pick something
  • Action! Need more regular team-wide buy-in
    • Meetings?
  • Action! Research how other teams do specs (e.g. Reading Web team) NOT DONE
  • Action! We need a standard QA rigor, engineers to design a QA acceptance criteria for all testing


Worked WellEdit

  • Productive changes to syncing with design
  • Team meeting about personal communication and improving
  • Welcome Nirzar! (officially)
  • Days off :)

Worked PoorlyEdit

  • "Needs QA" column is in rough shape.
    • Cards are overlapping
    • BG: To elaborate: big QA backlog means we can't really run regression tests
  • Still struggling as a team with kittens during estimation meetings
  • TestFlight: need "reliable" "infra" for "continuous" "delivery". especially for "bleeding edge" channels & "QA"

Confuses UsEdit

  • How are we defining "done"?
  • How do we feel about the "planning meeting" pilot?
    • Still need a prioritization meeting?
    • Monday vs Friday?
  • Optional grooming? (all my grooming is optional)
  • Alpha survey


Top three items, from "Worked Poorly" and "Confuses Us" (if short on time)Edit

Actions ItemsEdit

  • Action! Research how other teams do specs (e.g. Reading Web team) [BRIAN/JOSH]
  • Action! We need a standard QA rigor, engineers to design a QA acceptance criteria for all testing [TEAM]
  • Action! Groom QA column [JOSH]
  • Action! Assign a day of the week that we regularly release? Email thread [JOSH/TEAM]
  • Action! Schedule a team-wide regular planning meeting [MAX]
  • Action! Let's talk about how we define "done" [MAX]
    • New columns in Phab