Some thoughts on CAS Meetings

Summary of points from CAS Community Leader, John Palmer  on what makes a good CAS Community meeting, building on his own experience of running a successful community in the Malvern area for several years..

What makes a good CAS Community Meeting

  • Well attended (with at least one month's notice of meetings to ensure maximum promotion and gain maximum attendance)
  • Regular meetings (usually at least once per term)
  • Collaboration with local University
  • Useful content - focus of every meeting is to support computing activities in the classroom
  • Long-term impact from attendance
  • Feedback from attendees in order to offer targeted meeting programmes in the future
  • Ideas to take-away
  • Range of contributors / topics
  • Curriculum development
  • Training
  • Extra-curricular
  • STEM Links
  • Thoughtful location / timing of meetings

Planning

  • Make your plans at the start of each term and advertise the community meeting for that term
  • What is next?
  • Remember to be realistic about what is achievable.
  • Consider: Is the reach of CAS in the region continuing to grow?
  • Are there strategies/approaches for reaching beyond those who already know about CAS?

Problems?

  • Make contacts, find out what people want?
  • Look at CAS Online for CAS Members not attending meetings
  • Use the CAS resources
  • Contact  compatsch@bcs.uk
  • Request your local outreach person to support