{'fraction_non_alphanumeric': 0.019013666072489603, 'fraction_numerical': 0.0106951871657754, 'mean_word_length': 5.5271317829457365, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Understanding our Human Resources: District LeadershipEfforts at Understanding CS Education Implementationin Their Own Buildings

Computer science education research has primarily focused on teacher and student outcomes. Both teachers and students move through educational systems that have both direct and indirect effects on equity, quality, and implementation. Prior research has shown that there is a gap in enthusiasm and perception of importance of CS education between teachers and school leadership [2]. Additionally, many CS education studies have reported teacher attrition after professional development due to institutional barriers [3,4]. The recent report released by Google [2] mentions implementation 34 times and highlights the barriers faced by teachers and students when the systems are not aligned with the goals of individuals. In this poster we present data from 63 district teams participating in CSforALL SCRIPT workshops [1]. During the workshops, teams were asked to self-assess against a rubric signposting the growth toward high-quality CS education implementation and set goals for themselves to increase rigorous CS education instruction and equitable participation of students. This paper analyzes a subset of the 1023 goals collected by CSforALL to date [5], specifically focused on the goals related to landscaping, or district identification of resources and needs. This data corpus is comprised of 98 goals set by 38 school districts. Analysis takes a mixed methods approach, sharing quantitative data about the focus of the goals, as well as a qualitative analysis of how leadership teams sought to gain information about their own implementation.