@shereefb and I stumbled across this issue while thinking through some software stuff. The problem is that team leads need to be available to later cohorts on the same "interval" / cadence.
This is incredibly complex. My recommendation is to punt on "dynamic cycles" for v0 (maybe forever?), and instead come up with one "master schedule" that is at least 40 weeks long that ensures that team leads will be available when needed.
Criteria
Define the success criteria for this issue. What must an acceptable solution include?
Principles razor
In order for an issue to be marked as passing, the proposed solution must be aligned with our principles. Check off the principles that this solution is consistent with.
[ ] Cultivate a learning community.
[ ] Prioritize scale over quality
[ ] Align incentives
[ ] Build a team game
[ ] Trust people's intentions and potential
[ ] Enable self-organization & self-determination
[ ] Map feedback loops
[ ] Optimize for agility
[ ] Simulation not preparation
[ ] Sustain the tension between individual and collective gain
Context
@shereefb and I stumbled across this issue while thinking through some software stuff. The problem is that team leads need to be available to later cohorts on the same "interval" / cadence.
This is incredibly complex. My recommendation is to punt on "dynamic cycles" for
v0
(maybe forever?), and instead come up with one "master schedule" that is at least 40 weeks long that ensures that team leads will be available when needed.Criteria
Define the success criteria for this issue. What must an acceptable solution include?
Principles razor
In order for an issue to be marked as
passing
, the proposed solution must be aligned with our principles. Check off the principles that this solution is consistent with.