@antoviaque From next year, I will be working a 4-day work week instead of my current 5-day week. I’ll be taking Fridays off, which means I won’t be able to attend these sprints. But I’ll watch the recordings and take a look through the chat log every two weeks so I’m up to date with what’s going on. I’ll also keep in touch with the team on the forum to let them know what I’m up to, and that I’m available for UX help if they need it.
I’m on leave from tomorrow so won’t be able to make this either. Sheez, this post is making me seem really lazy , but I’ll be back fully refreshed and ready to go next year!
The results give Wednesday December 22nd 5pm UTC as the best slot for next week - so I’m moving next week’s meeting to that time.
End of sprint async update
FYI, for sprint updates, to keep them async and help structuring them, I’m thinking of experimenting with using Friday to post them. Any objections to that? If that sounds good, I’ll use it for the retro / end of sprint checkin, by posting a form for it there on Monday, ahead of the meeting on Wednesday.
Tentative list of questions, in case you have suggestions:
How did you feel about the sprint? (1-5 mood scale)
How much of your sprint goals did you complete (1-10 numerical scale)
Checkin - What did you accomplish this sprint? (free text)
Retrospective - What went well with this sprint? (free text)
Retrospective - What should we improve with contributors sprints? (free text)
To the other core contributors – please take 5 minutes to post your update for the sprint! Especially if you can’t attend it tomorrow due to the holidays. It will be important to use the feedback in there, to know what to improve, and what worked/didn’t work.
Responses so far (I’ll update it shortly before the meeting tomorrow with the rest of the answers sent in the meantime):
Hi all! As discussed at our meeting today, I’ve made a thread for us to do intros. Looking forward to hearing from you. Core Contributors Introduction Thread!
And here is the recap, including the action item you just completed @sarina
Improvements we’ll make
Allow everyone to add a list blockers to the sprint planning meeting’s agenda, and focus the meeting on this, the rest being done more asynchronously (assignee: @antoviaque )
Spend less time on intros during sprint planning to focus on the rest, by moving the introductions to a thread on the forum (assignee: @sarina )
Collect more insight into each others work to be able to collaborate more. Be familiar with other contributors’ areas of knowledge to get a sense of what they are working on and where they can help. This is going to be done mainly by continuing to do formal sprints like this one, but also by collecting areas of expertise and interest in the intro thread @sarina is collecting (assignee: none needed)
Discuss how to have better testing and sandboxes when preparing new releases, shared with the whole community (assignee: @ghassan )
Clarify the question about points to improve in the retrospective checkin, to also list what went wrong during the sprint, not just what we need to improve in sprints management in general (assignee: @antoviaque )
What went well
Collaboration with BTR and core contributors
It was good to meet everyone for the sprint planning, and hear about what everyone is working on. , The Remote working session for the upstreaming course produced a lot of work — it also energized the contributors community around that project.
Maple was released
Translations
We started having sprints and we are starting to communicate a lot better among the CCs.
Got prompt review (< 48h) when needed
Pretty much everything , Quick reviews, nice communication, friendly and smart people
Able to complete goals
Scheduled effort and hours planning for Transifex Working group
To save time during the meeting, the introductions have been moved to this thread Core Contributors Introduction Thread! (post yours if you haven’t already!) and I’ll send a sprint checkin form via friday.com (make sure to monitor notifications from there). It will contain the following two questions:
What will you work on in the upcoming sprint, starting next week?
Any blockers, or anything that could help you?
I’ll post the results here in a spreadsheet, and the “blockers” will be what is being discussed during the meeting.
Updated agenda
1) Priority tasks
Review any urgent or important community task which are missing an assignee
Find assignees for each of them
2) Blockers
Review the list of blockers mentioned in the sprint planning checkin by anyone
We are still missing a lot of updates – so core contributors, please search your emails for an email from “Friday hello@mg.fridayfeedback.com” titled “Core contributors - Sprint planning: please add an update”, and submit it today so we can compile the list of topics to discuss at the planning meeting. Thanks!
Btw, also note that I’m currently sick, so I won’t be able to attend the next meetings (it’s not too bad, but it’s a bit incapacitating for a time: Lyme disease). @sarina would you be able to cover for me and lead these meetings in the meantime? I’m happy to take them back over when I’m better, though it would be up to you. Otherwise @gabrieldamours would you be willing to cover for me there?
Hi @antoviaque@gabrieldamours I am happy to lead it as well. @antoviaque could you possibly add me or Gabriel to the Zoom meeting so we can start it, or change the invite to use my zoom?
Thanks! I’ve tried to add you both, but Zoom complained that he couldn’t find your email (I gave your tCRIL one), so only @gabrieldamours was added as a host. Let me know which email I should use to add you on Zoom, and I’ll add you too.
Sorry, I think I missed the deadline for this? and now I can’t figure out any way to add my check-in. I did get an email but every time I click the link it makes me log in to Friday all over again, and takes me to a generic Friday home page.
@braden@sarina The issue with the checkin seem to have been that the checkin was being sent every two weeks, but on the wrong week. There didn’t seem to be a way to adjust this, so I’ve recreated a new checkin for this week’s meeting - hopefully creating it now will set it with the right bi-weekly schedule. I’ll keep an eye on it this week, we’ll see if it sends the notifications correctly – let me know if there are any issue.
@sarina Btw, I’m getting better, but I won’t be able to join this week’s meeting again – I should however likely be back for the following one. Would you mind leading again the one from this week?
No problem, @antoviaque . Just be sure to add myself or @gabrieldamours as host for the zoom meeting. I think you’ll have to use my “official” email – scanelake [AT] tcril
Ah cool, thank you! I was really confused about when these updates were due, but having the reminders come in on the right week will help
So if I understand correctly the next one is due 4 Feb?
Is that “before” 4 Feb UTC, so the deadline is really 3 Feb EOD?
Friday.com is showing me as “all caught up”, but I know I haven’t posted one yet, and I can’t figure out how to add one without going via the notifications bar
For adding your email, I was still getting an error when trying to make you an admin, so maybe it is because your email isn’t part of our org? I’ve tried adding you, but looks like you’ll need to accept it. Alternatively, I could replace the Zoom meeting URL for tomorrow with one you would provide?
I think a good deadline would be Wed EOD (Feb 2nd this week) – that way it gives Thursday to check that everyone completed it, to turn it into a spreadsheet, and to read it async ahead of time.
@jill Hmm, that’s strange, I don’t see your update, while other people’s updates are there, and you are listed in the org. Could it be that you are logged in with a different account? It should be with your OpenCraft email. I’ve just resent the reminder email to those who haven’t filled the checkin yet, see if you got it. If not, see what you get by going to https://my.friday.app/reports/check-ins/f9811694-da15-474c-abee-33f91be8b240 ?