Wikimedia Apps/imported/Retrospective-July 31 2015

From mediawiki.org

Android[edit]

July 31, 2015

Previous Retrospective Actions[edit]

  • Alpha builds not working, https://phabricator.wikimedia.org/T104190
    • Action! Get on Yuvi's ass, press him to set up nginx [DMITRY] DONE
  • QA
    • Clear delineation of what two days Elena QAs (2 days for Apps, not just Android)
    • Working closely with Elena when she QAs
    • Action! Talk with iOS about splitting QA resources [DMITRY] NOT DONE
  • When does something go from alpha into beta (Design is unceratin about how long do we have to see something in alpha and make fixes)
    • Action! Android team to discuss internally [ANDROID, then disseminate] DONE

Additional Previous Actions[edit]

  • Action! Try a standup or scrum of scrums style meeting to improve coordination with mobile web and communication across Readership overall [Kristen] DONE-ish (2nd part) ONGOING (ADAM to email engineers to ask about meeting) DONE
  • Action! Clarify what devices/configurations are supported in Android/strategies for support, deprecation [Stephen] IN PROGRESS
  • Action! Get more android devices [ADAM] IN PROGRESS
  • Action! Kristen/Dmitry/Bernd to continue conversation and distill out to team. [MAX to follow up] DONE


Worked Well[edit]

  • Developer to developer conversations.
  • our velocity seems really good lately
  • velocity
  • attention to detail
  • Lots of effort by whole team to make a quality release.
  • good in-depth technical discussions (e.g., proguard)
  • good balance of user facing vs. tech debt stuff+
  • nice work on fixing link preview issues
  • data stories got in and are actively worked on
  • bernd's doing a good job handing some things off before paternity leave

Worked Poorly[edit]

  • time splitting between projects - which is, of course, kind of expected :( I remind again - please, ask explicitly if something requires QA attention in a timely manner
  • a bit more love from Design? :) (hefty Design signoff column) (although there's still time left in the sprint!)

Confuses Us[edit]

  • When does the "Points attempted" value get calculated? Does it get adjusted during the sprint when we pull in new storied during the sprint?
  • sometime I am not sure if Design should look first(before QA)


Top three items, from "Worked Poorly" and "Confuses Us":[edit]

Only 4 :)


Additional Action Items[edit]

  • Action! Talk with iOS about splitting QA resources [DMITRY] NOT DONE
  • Action! Clarify what devices/configurations are supported in Android/strategies for support, deprecation [Stephen] IN PROGRESS
  • Action! Get more android devices [ADAM] IN PROGRESS
  • Action! Get Samsung devices? Figure out which devices are most relevant. High pixel density devices, Galaxy S, etc. Adam to share devices analysis
  • Action! Discuss velocity calculation with team [MAX]


iOS[edit]

July 31, 2015


Previous Retrospective Actions[edit]

  • Action! Try a standup or scrum of scrums style meeting to improve coordination with mobile web and communication across Readership overall [Kristen] DONE-ish (2nd part)
  • Action! Make an effort to call out cross-team considerations at tech lead sync up [ADAM]
  • Action! Ask Jon Katz to focus on the cross-coordination aspect of his role in order to improve alignment across web and apps (eg communicating and planning what features make sense on what platform, help w/lead images) [JK]
  • Action! Try separate platform option for retro [MAX]
  • Action! Try some new manual QA methods? Try a "testing party" where we try to produce crashes that users are encountering [BG] ONGOING
  • Action! Explore automated scenario & fuzz testing [BG/iOS]
  • Action! [ONGOING] Email thread is happening about the lack of CI. What is the priority? [ADAM] DONE
  • Action! Make an effort to call out cross-team considerations at tech lead sync up [ADAM]
  • Action! Ask Jon Katz to focus on the cross-coordination aspect of his role in order to improve alignment across web and apps (eg communicating and planning what features make sense on what platform, help w/lead images) [JK]


Previous Retrospective (Android) Actions[edit]

  • Action! Clarify what devices/configurations are supported in Android/strategies for support, deprecation [Stephen] IN PROGRESS
  • Action! Get Elena better/more devices/OSes [DMITRY]
  • Action! Kristen/Dmitry/Bernd to continue MCS conversation and distill out to team. [KRISTEN/DMITRY/BERND]


Worked Well[edit]

  • it's great to get explicit requests and reminders - really appreciate it. Thx Brian!
  • New gh workflowz!
  • Refactorings
  • WFH
  • Kaity taking her prototypes to the streets of Mexico
  • Native View, with images from the lead!!!!!!
  • Gestural Swiping
  • Build moved pretty fast
  • Corey organizing and taking the lead for the new native pieces+1
  • Working with design on new UX flows
  • Engineers dealing with uncertanty with panache
  • Loving the code coverage and automated travis builds - less manual work +1 (seeing the coverage % is way cool)
  • Fastlane: cutting builds has been smooth lately+1 - need to make improvements, but still at a good starting point
  • Code review

Worked Poorly[edit]

  • Street tacoslol - poor monte
  • Cures for flus and viruses (2 hr emergency room visit + prescriptions was < $150US!!!)
  • Man power (late entry)

Confuses Us[edit]

  • Still some unknowns about 5.0 - but getting more clarity each week
  • If we need to be tackling 3 epics at once (can we reduce some scope/risk and release sooner)?
  • How/when do we get Elena testing 5.0 - hard to know until things stabilize more

Top three items, from "Worked Poorly" and "Confuses Us":[edit]

Only 4 :)


Additional Actions[edit]

  • Action! Try some new manual QA methods? Try a "testing party" where we try to produce crashes that users are encountering [BG]
  • Action! Figure out testing strategy going into final month of 5.0 [BG/iOS]
  • Action! Talk with Android about QA's availability/resources. [iOS/ANDROID TEAMS]