Readers/Web/Team/Retrospectives/2015-06-23

Wayne's World

Notable events

• Teams merge!!!!!!

Absences

• End of Sam's Disney adventure
• Rob coming back

Velocity

https://docs.google.com/spreadsheets/d/1WhuTM1UBAVwFYJf6C6Rrd_INYlzKTa1oCSQnpvpougg/edit#gid=2 42 points attempted, 18.5 points completed (avg is 18)

Action Items

Top actionable items to address

• Editing team communicating with us about objectives/blockers++++
• Pinging Kaity / design availability++++
• If there is a negative feel (from last retro) that we are 'spinning our wheels' I just want to be sure everyone is bought into spending 1/2 qtr on process dev, and then 1/2 qtr on speed++

Actions

• Action! Run script that generates changelog since last deploy (and send to mailing list)

https://phabricator.wikimedia.org/T100296 [ONGOING, part of sprint planning]

• Action! Follow-up email to mobile-l with details – motivation, strategy – of QA day [SAM]
• Action! JonK to chat with Kaity about design support for q1
  • If something is urgent, Kaity would like a ping by chat
  • Kaity to look at Phab more
  • Kaity will get irccloud installed on the phone?
• Action! Adam to arrange meeting to discuss Editing/Readership communication in general, and ve in mobile in particular--distribute outcome to team
• Action! Joaquin to Send outcome of engs meeting to discuss eng work to all and ask for opinion.

What's been working well?

• QA day ++++
  • More awareness on what we are pushing to prod.
• Simplified weekly deployments
  • Faster deployment schedule (clearer overall)
• Work and planning towards Q1+
• A clearer happier environment to work in (things seem less chaotic)
• slowing down
• The red limited columns helped me personally (I took on smaller tasks/experiments whilst waiting for code review when I was contributing to the problem)
• Developer backlog finally getting some attention. Developers feeling equals to design/product rather than non-equals.
• BarryBot (? do others agree) ++
• JK: combining the teams? +++
  • Team back together
• Taking ownership like the apps teams

What hasn't worked well

• Pinging Kaity / design availability++++
• Editing team communicating with us about objectives/blockers++++
  • Editing team & contributor creating a ton of style regressions.+
• Sam staying on top of the sign off column
• Simplified weekly deployments

What is confusing

• The overall strategy for mobile (or lack of it). Readrs being sent to apps but VisualEditor on mobile web?! (wahh) +
• What to do with florian's editing based patches. Getting a roadmap about editing plans for mobile.
• If there is a negative feel (from last retro) that we are 'spinning our wheels' I just want to be sure everyone is bought into spending 1/2 qtr on process dev, and then 1/2 qtr on speed++
• releng deployment process changes