Hi All,
Earlier today we had our bi-weekly FxA developers retrospective, our
regular chance to all get together and brain-dump on what's working,
what's not, and what's outright puzzling us right now. We touched on
the following points:
* The theme from last time was "feeling connected" and we did a pretty
good job of following up on the proposed experiments:
* Sending out email summaries after each meeting seems to have been
very well received, so let's keep doing that! We'll have to ensure
that we can evenly distribute the workload of this going forward,
perhaps by having a rotating roster for note-taking.
* By contrast, the fxa_watercooler vidyo room was a bit of a bust,
with timezones making it hard for many of us to overlap in there
in a meaningful way. Several folks reported not being aware of it,
so lets try it out for another two weeks before deciding on its
ultimate fate.
* In general there seems to have been more async discussion on the
mailing list and it's helped us feel more connected.
* The most prominent new theme branched off from Sean's email to
fxa-staff about the "Buddy System", and trying to ensure that we're
not working alone:
* Let's commit to fewer things next quarter, especially since it'll
be a short one with the all-hands and the holidays. This will stop
us from feeling like we have to spread the team too thing to cover
all the bases.
* We should ideally have only 2 or 3 features in "building" at once,
so that we all have more bandwidth to collaborate on them. In
theory
* Let's try to set ourselves to succeed at this in Q4, by focusing
on metrics for our OKRs, by prioritizing our features by their
impact on those metrics, and by working through them deliberately
in that order.
* Alex's recent summary of the FxA-specific portions from the SUMO
feedback report was very very useful, and we should keep doing that.
* We've recently starting giving :rfeeley and :adavis a dedicated slot
at the start of the FxA web coordination meeting, and it's been very
valuable in surfacing issues that need prioritization from their point
of view.
* There was more discussion about our review process this week, with
some things to watch our and some things to try:
* The "@fxa-devs r?" convention that we've been experimenting with
sometimes encourages a feeling of "well someone else can do it",
although it also helps us feel comfortable with offering drive-by
feedback.
* If you're reviewing a large PR, please ensure you've read the
relevant portions of the feature-doc, that's what they're for :-)
* It would be fun to experiment with a github bot that can pick
someone for review, nag you about outstanding reviews, and other
such dev-process-management tasks.
The take-away actions from this week are on Alex and myself, to ensure
that we have the structure and support in place for us to succeed at
"dont work alone" in Q4. Async suggestions on how that might look in
practice are definitely welcome!
Cheers,
Ryan
_______________________________________________
Dev-fxacct mailing list
[email protected]
https://mail.mozilla.org/listinfo/dev-fxacct
