Confirmed users
2,473
edits
DeveloperServices/TeamMeetings/2015-06-30: Difference between revisions
DeveloperServices/TeamMeetings/2015-06-30 (view source)
Revision as of 18:28, 30 June 2015
, 30 June 2015→Other business
m (gps) |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 54: | Line 54: | ||
== Other business == | == Other business == | ||
* [lmandel] Whistler recap | |||
** What worked? | |||
*** Breakout rooms (non allocated time), office hours | |||
*** DXR demo + discussion was really good | |||
*** Tuesday all-hands was good | |||
** What didn't? | |||
*** Lots of discussions in our breakout room, people who weren't part of our org and talking about non work (on phone) | |||
*** Agenda helps drive meetings to a useful place | |||
*** Too many people in a discussion typically results in nothing getting done | |||
*** Thursday all-hands wasn't very valuable | |||
*** Tricky to meet with groups in different hotels | |||
** What should we do differently next time? | |||
*** More opportunities to engage with more orgs - notably Firefox team, talked tools in Firefox all-hands, cross breeding can't happen if sessions are scheduled concurrently | |||
*** Get things done by scheduling things early in the week | |||
* [lmandel] Adding bug links for stand-up items | * [lmandel] Adding bug links for stand-up items | ||
** Dev work is largely tracked in bugs already. fubar, bkero and I discussed tracking more ops work in bugs as well. Can we start to link to bugs in our stand-up reports so that it's easier to follow-up on work? | ** Dev work is largely tracked in bugs already. fubar, bkero and I discussed tracking more ops work in bugs as well. Can we start to link to bugs in our stand-up reports so that it's easier to follow-up on work? | ||