He @may21-cohort, you’re receiving this recap almost a week after our Session 12 Wrap-Up. Here’s the chat link. I wanted to thank those who joined for the excellent conversation and contributions. You’ve been incredibly supportive of one another, especially with troubleshooting things like the MOST deadlines. In this recap I want to start by emphasizing two action items:
- Complete a Course Evaluation (for Sessions 1-12). We’ll have another evaluation at the very end of the Rebus program, in another 9 months.
- If you haven’t yet responded to this topic thread, please do so by the end of this week with 1-2 goals for you and your team to touch base on at the next TSP check-in (Sept 16th). I’d love to hear from at least one member from each of the teams!
Here are some links from our session:
We hope that 12 weeks of the TSP have helped you see that the open publishing process is not as mysterious or complex as you may have thought! You may have seen some patterns forming between each of the stages we’ve covered. While we’re not doing an in-depth overview of each stage, we’re hoping that you can keep in mind these general principles to guide you along your way:
- Plan ahead and revisit your approach at each stage (think through the process, create supporting documents, and meet with your team before diving into action)
- Be public about the work on your project (so everyone on the team is on the same page, and so others know how to chip in or offer support)
- Consider your audience and their needs from the very beginning (so your resource is more accessible, usable, and valuable)
- Collaborate and provide pathways for people to join (different perspectives can strengthen your resource, and more people can help share the workload)
- Nothing is set in stone or unchangeable (your resource can mould to fit changing needs or goals, and can be easily modified even after it is released)
- Books and communities go hand in hand (you are creating both an OER and a group or team around this OER who is invested in using it and seeing it live on)
- Remember that everyone involved in these projects, yourself included, is human (so be conscious of workloads, take breaks when needed, and focus on keeping the team connections intact)
What to expect at our monthly check-ins
Our first check-in is September 16th. Remember that all our check-ins are already on your calendars, and will be at our usual slot on Thursdays at 12:00 PM EST.
The check-ins are a space to get support from Rebus and your fellow cohort members. You can share updates, ask detailed questions, talk through challenges, and go into as much detail about how principles are applying to your project as you want. You can use monthly check-ins to set goals for progress and hold yourself accountable.
While the structure of these check-ins may change as we go, it’ll only be in service of your projects and to support you better. Keep your eye on our Rebus forum. It is a place to go to ask for help and offer support, share progress (everyone can start a new conversation) in between check-ins. Use the cohort tag @may21-cohort, tag individual members, as needed, and if you are tagged in a discussion, please take a few minutes to respond. I will moderate the discussion, but it will only be fruitful if we are all actively participating.
Finally, you may want to come back to all the documents we have referenced over the past 12 weeks. All these resources are collected in a Curriculum Hub — hopefully this is more easily navigable.