With daylight savings coming in and out of force around the world our meeting times need to change. In previous years we’ve simply flipped the AMs and PMs about but this year our team has grown and we need to include more timezones. Realistically it will no longer be possible to find a timezone that fits everyone.
The next best approach is to have two meetings that alternate in times in such a way that everyone can attend at least one of them.
Increasing the number of meetings like this makes it seem tricky to keep having both a Product Curation meeting and a Delivery Train meeting. So I propose that we change these meetings to be ‘Horizon 1’ meetings.
Horizon One Meeting
To cover both of the previous meetings in one the agenda will need to look something like:
- Look at the board and issues in play as we do in delivery train to check in on Test, Code Review, In Dev and all the current prioritised bugs.
- Go through all the Epics/Features in play for an update on where we are at
- Go through the upcoming priorities this horizon to hear an update on what’s in inception and design processes enroute to dev ready.
As we won’t all be at every meeting it is likely that we won’t always have someone to update on everything live. Could we manage our notes in a similar way that we do for Product Curation? Could we manage our notes with a discourse wiki page and standard format that we all fill in to ensure that everyone can keep up with the overview of our work?
In the above format this meeting will exclude the work that is currently not yet in inception or delivery. We will need to have another meeting to ensure that the work that is being prepared and prioritised to come into the pipe. Perhaps something like a Roadmap meeting…
Currently we don’t handle the process of planning ahead of Horizon One very well. I believe there are others in the product-circle working on processes for prioritisation so I only mention this here because not mentioning a meeting to plan beyond Horizon One would be a mistake Just to note that this meeting doesn’t need to be as regular as the above… perhaps monthly. Essentially this would be a place to present, organise and agree on the different priorities that have emerged from:
- Instance manager/Community needs
- Support team case loads
- Dev priorities
- Design priorities
As this is quite pressing, and hopefully not too controversial, I’d like to propose that we press on finding two suitable timeslots for our Horizon One meetings so that these can start from April.
I have created a LettuceMeet for 24hrs Mon to Fri. It would be really helpful if everyone in delivery could add a rough guide to when they can meet. Ignore the dates… treat it as a generic week. Try to be flexible but realistic.
From this I will try to find two times that everyone can attend… wish me luck!
this was meant to be a short post. Sorry!!