Works for me. That means that we can still start with UX/PM and just switch to dev as soon as we're done, correct?
-- Alex Davis // Mountain View Product Manager // FxA & Sync (415) 769-9247 IRC & Slack: adavis On Wed, Oct 26, 2016 at 10:13 AM, Shane Tomlinson <[email protected]> wrote: > I facilitate 4 of the above meetings: > > * Monday web UX meeting > * Monday web coordination > * Thursday frontend standup > * Thursday web bug triage > > 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. > > 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. > > 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. > > 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. > > Concrete proposal: > > 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. > > Yae? Nay? Alternatives? > > Shane > > > > On Tue, Oct 25, 2016 at 7:18 AM, Ryan Kelly <[email protected]> wrote: > >> On 25/10/16 17:08, Ryan Kelly wrote: >> > * We've got a lot of meetings. Can we optimize some away, or >> > perhaps reduce the list of attendees? We agreed to continue >> > this discussion offline. >> >> In the spirit of which, this mailing list is as good a place as any to >> continue the discussion! >> >> The meetings that the FxA team currently has on its books include: >> >> * Monday web UX meeting >> * Monday web coordination >> * Monday show & tell >> * Monday sprint planning / retrospective >> * Tuesday backend catchup >> * Thursday frontend standup >> * Thursday web bug triage >> * Thursday product meeting >> >> Which is indeed a lot! Did I miss any? >> >> Some options for reducing meeting burden include: >> >> * Narrowing the scope, e.g. making more of the meetings optional >> for more people. >> >> * Cancelling some entirely, and moving their contents into >> e.g. async communication methods. >> >> But I don't want to dictate anything here. I'm open to any and all >> suggestions. So - thoughts? >> >> >> Cheers, >> >> Ryan >> _______________________________________________ >> Dev-fxacct mailing list >> [email protected] >> https://mail.mozilla.org/listinfo/dev-fxacct >> > > > _______________________________________________ > Dev-fxacct mailing list > [email protected] > https://mail.mozilla.org/listinfo/dev-fxacct > >
_______________________________________________ Dev-fxacct mailing list [email protected] https://mail.mozilla.org/listinfo/dev-fxacct
