Developing an Agenda

‚Äč

    1. Flow of the week

      1. When to start sessions

        1. We started ECS, CSD, and CSP on Monday, the administrator and counselor workshops on Tuesday, and the elementary workshops on Wednesday.

        2. While this staggered the number of attendees, if everyone had started on Monday morning it would have provided more energy and made clearer the intention of highlighting the need of multi-stakeholder CS education implementation.

      2. One day workshops

        1. Single day workshops may be more attractive for busy administrators and counselors, but they allow less time for exchanges with other stakeholders.

        2. Consider extended 2-day workshops, or intentionally integrating administrators and counselors with teacher workshops. Facilitators reported that having administrators in their teacher-focused workshops provided fuller discussion and understanding of the factors at play when implementing CS education.

    2. Summer of CS Excursions

      1. Focus on one? Offer more than one?

      2. How to encourage one-day participation?

    3. Day-of Events (Policy, etc.)

      1. Spread out

        1. We decided to have both our Creativity Breakfast and Policy Luncheon on the same day (Tuesday), so that counselors and administrators could participate in both. This proved to be chaotic and stressful.

        2. We would suggest having the panel luncheon on Monday (where you can highlight the multi-stakeholder nature of the Summer of CS) and the breakfast on Tuesday.

      2. Choosing topics for events

      3. Panel

        1. A panel provides the opportunity to hear a deeper discussion between different perspectives on a topic.

        2. Theme

          1. When creating a panel, select a theme, and be sure to make decisions with adherence to that theme. We wavered among themes of Equity, CS Policy, Multi-stakeholder involvement in CS, as well as the story of CS in California

        3. Panelists

          1. Seven (7) panelists participated in our panel, but in order to get deeper discussion and understanding, we would recommend no more than 3 or 4.

          2. Consider the diversity of your panel, including their role in CS education, gender, ethnicity, race, and sexual orientation.

        4. Duration

          1. Devote at least 30 minutes to the panel session with at least 15 additional minutes for Q & A (45 minutes total).

      4. Facilitator debrief

        1. At least days 1, 2, & 3 should have a brief debrief meeting with facilitators

          1. Facilitator needs

          2. Participants needs

          3. feedback/adjustments