@Natalie Larino -

I’d be happy to chat about this - a sprint-based cadence can be used for different types of work if the work items lend themselves to be completed within the sprint and there is a desire to potentially release what has been completed within each sprint. Otherwise, a flow-based approach could also be considered.

Kiron

Hm, interesting. I’d say the former is what we’d aim for, we sort of have to work in batches just with the nature of our work, for example, for events - we need to have it posted, we need event info/speaker bio etc, before we can give it to the social team. At the same time they have to work with outside stakeholders to have the event marketed on various platforms (blog, newsletter) while the community team, user leaders, and speakers should be posting about their event within their own networks. 

@Natalie Larino -

This can be done using sprints, but it sounds like there are lots of inter-dependencies between the activities culminating in an event so a traditional scheduling approach would also work. Let me know if you want to chat about this…

Kiron