Should Sprint Goal be akin to OKR.
I like ‘policies’ over ‘process’.
+1 on the ‘behavior’ suggestion.
+1 on the ‘relationship’ suggestion: Ackoff: “It is about the *product* (not sum) of the *interactions* (relationships) of parts (humans) of the system (team).
Rename “impediments” to “accelerators” as is has a positive connotation and their removal will accelerate the team, serving customers and users.
How about “Build Crew”?
Or maybe shift it more the towards outcome or impact the “Build Crew” is aiming to achieve. Any suggestions for names?
Rename the To Do state to “Ready to Build” and set a WIP-limit of, say, 6 on it. Maybe even a low water limit of 2 to trigger the Product Owner to timely replenish it.
TMO the Sprint Goal for the next Sprint may even be set in the current Sprint. So yes, decouple setting the Sprint Goal from any event. Just make sure you (always?!) have a Sprint Goal, get closer to it every day and evolve it based on new insights.
I’d say the Daily Scrum is a meeting open to anyone, yet only Development Team members *participate* (i.e. DT members are read-write and the rest is read-only).