Identity/Firefox Accounts/Meeting Notes/2016-04-27 Web Coordination Retrospective

From MozillaWiki
Jump to: navigation, search

FxA Web Retrospectives, Wednesday 2016-04-27

Time period covered: 2016-04-11 to 2016-04-25 Major theme: cleanup and verify sign-in

Timeline/Events

  • fxa-83 for pb, vb, st
  • fixing what's broken, reverse merging, UX debt

Good

  • When we did start to communicate about individual responsibilities, fxa-83 got a lot more productive.
  • hopping on Vidyo is a much better way to transfer information quickly than GitHub.
  • small intermediate steps
  • getting in vidyo to chat (+1)

Bad

  • We didn't finish the last retrospective and vote on an outcome.
  • We didn't communicate well about individual responsibilities at the start of FxA-83. (+1)
  • being confused
  • devops confusion

More

  • making intermediate goals
  • hopping into vidyo for short conversations
  • DevOps communication: 5720e373b283f.jpg
    • list of stuff that needs to be included in the train
    • not exactly bad, but really "nice to have" ?

Less

  • not writing down as I go along in this process.
  • adding on to other folks' PRs
  • Stuff on the backlog in the content server.

Enjoyed

  • Picking up flowId stuff after such a long time.
  • Talking about issues or design over video, was helpful when github conversation got to long (+1)
  • Seeing long standing PRs get merged.
  • Getting back to normal (+1)
  • Action items!

Didn't enjoy

  • Being document guy on FxA-83.
  • The content server is HARD.
  • Causing confusion in the group.
  • The pressure of the "active" and "next" columns.
  • Shane's crappy internet.

Cluster

  • Communication seems like the big theme here?
    • When we did start to communicate about individual responsibilities, fxa-83 got a lot more productive.
    • hopping on Vidyo is a much better way to transfer information quickly than GitHub.
    • getting in vidyo to chat (+1)
    • We didn't communicate well about individual responsibilities at the start of FxA-83. (+1)
    • being confused
    • devops confusion
    • hopping into vidyo for short conversations
    • DevOps communication:
    • list of stuff that needs to be included in the train
    • not exactly bad, but really "nice to have"
    • Talking about issues or design over video, was helpful when github conversation got to long (+1)
    • Causing confusion in the group.
  • confusion
    • being confused
    • devops confusion
    • Causing confusion in the group.
    • adding on to other folks' PRs
    • When we did start to communicate about individual responsibilities, fxa-83 got a lot more productive.
  • others
    • not writing down as I go along in this process.
    • Picking up flowId stuff after such a long time.
    • Seeing long standing PRs get merged.
    • Getting back to normal (+1)
    • Being document guy on FxA-83.
    • The content server is HARD.
    • The pressure of the "active" and "next" columns.

Vote

  • Hopping in vidyo more often. (+1)(++1) ) +1 (
  • Clearly define each person's responsibilities at the start of a feature.
  • Make a note of what each person commits to.
  • If a feature is being worked on by multiple people, record in the document who is doing what.
  • Think twice before commenting on GH PRs - is it the right forum / would irc or vidyo be better?
  • Better wifi for Shane.