Readers/Web/Team/Retrospectives/2015-08-18

From mediawiki.org

Notable Events[edit]

  • JK came back
  • Strategy kickoff
  • KL muscles blew up
  • Rob still has baby
  • JK gets moustache
  • Jeff is attending Reading web meetings is Jeff back? it's a process

Absences[edit]

  • KL Out 08/10-08/17
  • Sam PT

Previous retro actions[edit]

Action! Circle back to team direction discussion post-strategy kickoff at next retro to see how we are feeling then [TEAM] DONE

Action! Email Rachel and Quim re: ECT help with Reading Web team offsite (Phab doesn't seem to be working-privacy settings?) [KL] DONE

Action! Meet to figure out next offsite steps, try to get travel sorted within next ten days [JO/KL] ONGOING

<Iceland or Portugal in October>

Action! Lock down location, $s, and finalize travel [KL]

Action! Review Reading Web Planning board before estimation to see what's coming up and weigh in [TEAM] DONE

Action! Move MFE tasks/bugs to MFE project; create queries for high priority bugs/triage [JOH] ALMOST DONE

Velocity[edit]

8 points (previously ~20) https://docs.google.com/spreadsheets/d/1WhuTM1UBAVwFYJf6C6Rrd_INYlzKTa1oCSQnpvpougg/edit#gid=2

Notes on velocity:

  • starting new extensions is hard; Jon pushing for more responsible (?) development
  • There were many dependent tasks; slowed down movement of stuff

---

Worked Well[edit]

  • Sign off notes from Joaquin
  • Upstreaming!
    • Bartosz upstreaming our ForeignApi code
    • mw.storage
    • experiments (in progress)
  • Killing code
    • login code
    • alpha code
  • Pairing is Caring
  • Integrate more with the org when doing QuickSurveys
  • Meeting with Bryan about ex-Mobile team why's [send to mailing list! :)] (yep, pending to do)

Worked Not Well[edit]

  • Joaquin's internet :P
  • Paring is Caring - start time and attendance and possibly a day after kick off is problematic? +++
    • Would like to have 1 on 1 sessions scheduled at random-but-agreed-on times
  • Still have lots of code debt - namely banner image/header (killing this sprint) and Gather (?) - bugs occurring there since not actively working on it right now - concerning
  • Things are very quiet in meetings / in IRC channel during day time +
  • No visible site improvements (but I guess this is accepted/understood?)+
  • Office move
  • Phabricator (dragging, typeaheads, ...)
  • Bad spirits due to re-reading old conflictive phab tasks while re-triaging and organizing with negative comments directed at people on the mobile web team and a general sense of disdain felt towards the people on the team. Also old tasks re-prioritized by people not working on them.

Confuses[edit]

  • what metric can we use to measure success of reading web +++++
  • What is #mobilefrontend-feature-requests for? Can we merge with #mobilefrontend [YES]
  • Prototyping and experiment, how will we do it++++

Top three items[edit]

  • what metric can we use to measure success of reading web +++++
    • JK: until we have an aspiration, it’s hard to know what to measure against
    • JK working with analytic on session and user level stuff
    • JDLR feeling disconnected from mission because I don’t know how to engage...what are we using quick survey work for?
    • AB: surveys will be used for data-driven approach to design changes, informing stra
    • JK: We should distinguish between feature-level goals and metrics (survey = info about users) V. top-level (reading = learning, with engagement as a proxy for now)

Action! Document how each feature ties in to our goals? What is the theory of impact for a given scope of work? [Product, techpros]

Action! Documentation for experimental work, including results, rationale [Product, techpros]

  • Prototyping and experiment, how will we do it++++
    • Need to get prototyping team thinking one quarter ahead
  • Paring is Caring - start time and attendance and possibly a day after kick off is problematic? +++
    • Would like to have 1 on 1 sessions scheduled at random-but-agreed-on times
    • Action! Set up a pairing session with another team member you haven’t paired with [TEAM]
      • Don’t forget to plan what you want to work on!!!
    • Action! Create a “pair-worthy” tag in Phab [SS]