action #135023
closed
Consider moving the retro out of the weekly or alternating either one size:S
Added by livdywan 10 months ago.
Updated 7 months ago.
Description
Motivation¶
We sometimes run out of time or feel we should have more time to discuss retro topics.
Acceptance criteria¶
- AC1: Retro has been moved out of the weekly
- AC2: An explicit decision has been made in the team how to continue after the experimentation period
Suggestions¶
- Alternate the weekly and the retro respectively
- Formally extend the weekly
- Explore other slots
- Come up with a new call that covers things like the roadmap which are otherwise part of the weekly
- Collect feedback over an experimentation period, usually 6 weeks
- Ensure our team wiki is up-to-date
- Make a team decision at the end of experimentation period which way to go
- Status changed from New to Feedback
- Assignee set to livdywan
Alternate the weekly and the retro respectively
I'm suggesting we conduct this as an experiment. This way we get the time we need for both calls and don't need to come up with a new slot.
On a related note we should also conduct another retro without our PO since we haven't done that in a while (just a one-off).
It seems my suggestion in Slack https://suse.slack.com/archives/C02AJ1E568M/p1695020030592429?thread_ts=1694784978.245389&cid=C02AJ1E568M was overlooked. Given the problems we hit in past weeks I don't see it feasible to just reduce the time for weekly coordination hence I suggested: "How about virtual coffee every Monday at 1000CET/CEST, and planning+daily every Monday at 1030-1150 (max) CET/CEST". And I don't see that a fortnightly weekly is giving enough motivation to get things done until the demo that we planned during this time. I forgot to bring up that given also feedback from stakeholders in particular including line managers I think we should still run a weekly which at least includes the demo part. So please let's reconsider before end of next week when we would have a "retro-only" slot according to your proposal.
In conversation in Slack we've come up with these additional ideas:
- "Planning" from 10-10.30 CE(S)T every Monday
- Look at New and Workable tasks in the backlog
- Check Next and Future tickets
- Handover of duties if not done at this point
- Availability/absence/vacation announcements
We're already doing this ad-hoc of course. The difference would be that it's easier for everyone to make time for a regular slot.
- Consider conducting the demo part of the weekly every week
This would alleviate too much time passing.
- Due date set to 2023-11-17
Setting a due date corresponding to 8 weeks so that's when we should try and reflect how this is going at the latest. Early feedback is of course still welcome.
- Priority changed from Normal to Low
Let's run that for the next weeks and then review
Just one observation on this. It seems like we were able to make good use of the time we had today.
- Subject changed from Consider moving the retro out of the weekly or alternating either one to Consider moving the retro out of the weekly or alternating either one size:S
- Description updated (diff)
We can track that in "Next" until we need to decide about the result of our experiment.
- Target version changed from Ready to Tools - Next
- Status changed from Feedback to Resolved
Having conducted another successful retro I'm assuming we are happy with it.
Also available in: Atom
PDF