<div dir="ltr"><div><div><div><div><div><div>I facilitate 4 of the above meetings:<br><br>* <span class="gmail-aBn" tabindex="0"><span class="gmail-aQJ">Monday</span></span> web UX <span class="gmail-il">meeting</span><br>
* <span class="gmail-aBn" tabindex="0"><span class="gmail-aQJ">Monday</span></span> web coordination<br>* <span class="gmail-aBn" tabindex="0"><span class="gmail-aQJ">Thursday</span></span> frontend standup<br>
* <span class="gmail-aBn" tabindex="0"><span class="gmail-aQJ">Thursday</span></span> web bug triage<br><br></div>A month or so ago, we decided to split the Monday Web Coordination meeting into two halves, one focused on UX/PM issues, the other focused on Ops/General Dev. The UX/PM half starts at 16.30 London time so that Ryan Feeley can attend before the Fx UX meeting at 17.00. The Ops/General dev begins at 17.00.<br><br>The last couple of weeks, the UX/PM meeting has finished early, but we haven't started the "Ops/General dev" meeting until 17.00. <br><br>These two meetings have a big lull in the middle, a lull that's not long enough for people to go about their daily business, but long enough to feel wasteful. From what I understand, the Ops portion is largely duplicated with the
Tuesday Backend meeting. Saying the same thing twice isn't really a lot
of fun.<br></div><br></div>I propose we reduce the scope of the Ops/General dev meeting so that John and Jon's time is not wasted saying the same thing twice and if we finish the UX/PM half early, we can just plow forward without missing anybody.<br><br></div>Concrete proposal:<br><br></div>Monday UX/PM meeting->Monday General Dev meeting. John and Jon's backend contributions can be saved for the backend meeting to avoid saying it twice. Their attendance would be optional, I enjoy having both of them there and value their input, but would not be upset if the decide their time is better spent elsewhere. We'll keep a full hour booked, but if we finish early, we get out early.<br><br></div><div>Yae? Nay? Alternatives?<br></div><div><br></div>Shane<br><div><div><div><div><div><div><div><div><div><br><br></div></div></div></div></div></div></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Oct 25, 2016 at 7:18 AM, Ryan Kelly <span dir="ltr"><<a href="mailto:rfkelly@mozilla.com" target="_blank">rfkelly@mozilla.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 25/10/16 17:08, Ryan Kelly wrote:<br>
> * We've got a lot of meetings. Can we optimize some away, or<br>
> perhaps reduce the list of attendees? We agreed to continue<br>
> this discussion offline.<br>
<br>
In the spirit of which, this mailing list is as good a place as any to<br>
continue the discussion!<br>
<br>
The meetings that the FxA team currently has on its books include:<br>
<br>
* Monday web UX meeting<br>
* Monday web coordination<br>
* Monday show & tell<br>
* Monday sprint planning / retrospective<br>
* Tuesday backend catchup<br>
* Thursday frontend standup<br>
* Thursday web bug triage<br>
* Thursday product meeting<br>
<br>
Which is indeed a lot! Did I miss any?<br>
<br>
Some options for reducing meeting burden include:<br>
<br>
* Narrowing the scope, e.g. making more of the meetings optional<br>
for more people.<br>
<br>
* Cancelling some entirely, and moving their contents into<br>
e.g. async communication methods.<br>
<br>
But I don't want to dictate anything here. I'm open to any and all<br>
suggestions. So - thoughts?<br>
<br>
<br>
Cheers,<br>
<br>
Ryan<br>
______________________________<wbr>_________________<br>
Dev-fxacct mailing list<br>
<a href="mailto:Dev-fxacct@mozilla.org">Dev-fxacct@mozilla.org</a><br>
<a href="https://mail.mozilla.org/listinfo/dev-fxacct" rel="noreferrer" target="_blank">https://mail.mozilla.org/<wbr>listinfo/dev-fxacct</a><br>
</blockquote></div><br></div>