I found this really useful, and I even attended! I suppose the chaos of us all trying to talk it through makes it hard to follow, so reading the summary made me feel "oh yea, that's what we discussed."
On Tue, Sep 13, 2016 at 4:25 AM Ryan Kelly <[email protected]> wrote: > > Hi All, > > Thanks to everyone for joining in on the FxA team retrospective today, I > found it super valuable and we had a lot of good ideas for things to > try. Here's my attempt at a broad summary of the things we discussed; I > will follow up with individual bugs or emails for some of the other items. > > What are we doing well? > > * We've been making use of the mailing list for async feature discussion > and demos, which draws input from a broader pool of people. Let's > keep doing that! > > * We've been regularly revisiting features in the "measuring" column and > getting better at explicitly closing them out. > > What could we do better? > > * Debugging test failures in the auth-server is source of slowness and > frustration. We've got an issue on file to improve this and we need > to make sure it doesn't fall off the radar: > > https://github.com/mozilla/fxa-auth-server/issues/1448 > > * Feeling connected and "in the loop" is an ongoing challenge in our > highly distributed team. Let's try two experiments to see if they > help: > > * Establish a "water-cooler" vidyo room for folks who just need > to hang out and see people's faces. > > * Send out a summary after every meeting, even those for which we > recorded a video. Much like this summary in fact. > > > I look forward to checking in on the results of these at the next > retrospective in two weeks time. > > > 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
