CSTAR _ Computer Science Team Analytic Resource

pdf

School

Regent University *

*We aren’t endorsed by this school

Course

4422

Subject

Computer Science

Date

Nov 24, 2024

Type

pdf

Pages

28

Uploaded by EarlHerringMaster1012

Report
CSTAR | Computer Science Team Analytic Resource Mahmoud Aliamer, Kristan Beck Elementary School Team Computer Science Department | Chicago Public Schools
Contents Usage Guide 1 What is CSTAR and why was it created? 1 Cultivating a mindset for computer science and creative problem solving 2 CSTAR 3 “Elements” and “Components” 3 Reading and using the rubrics 4 Elements at-a-glance 5 Leadership 8 Sustainability & Growth 10 Accessibility & Equity 12 Family & Community Engagement 15 Shared Joy 17 Common Threads 19 Last, but not Least 21 About the Computer Science Department 21 Our case for Computer Science Education 22 CS4All: Teaching computer science for equity and inquiry 24 References and Resources 26
Usage Guide What is CSTAR and why was it created? The Computer Science Team Analytic Resource (CSTAR) is a thinking tool developed by the elementary school team in the Computer Science department at Chicago Public Schools. We support 481 elementary schools in their journey toward providing CS4All – a thorough and comprehensive computer science education for every student, with an emphasis on doing so equitably and justly. Computer science education in Chicago is teeming with innovation. Every school community has unique needs, aspirations, areas of expertise, and areas for growth. Some of our schools are just starting their journey; some have been working at it for a number of years; some are figuring out where, when, and how to get started. We learned from our teachers and principals that there was a genuine desire for a thinking tool that could provide a structure to their discourse around computer science education, but maintain the flexibility to be useful to schools in a variety of contexts. This is not created as an evaluative guide or framework that lays out the “one true path” to CS4All. Our goals in producing this thinking tool are to: Empower school communities to have informed and organic conversations about computer science education Assist schools in identifying their current practices and priorities in computer science education, and Highlight connections between already-existing school goals and goals in computer science integration and expansion We are focused on taking a team approach to defining CS4All. The development of CSTAR was a team effort in itself. We have been learning from our experts – the teachers in Chicago Public Schools who continue to build their own understanding of computer science and use their learning to empower their students. We continue to lean on the expertise of our school communities and our research partners as we expand the foundations of our own thinking. The work of putting together this thinking tool was an exercise in openness, reflectiveness, and exploration. We want this to be a way for school communities to ask “where are we in terms of our students’ experiences with computer science? Where are we headed? Why are we structuring our work this way, and is that structure truly equitable? Who are we including, and why? Who are we excluding, and how do we fix it?” We hope that what we have created here affords schools the fluidity to define a path towards CS4All in a way that more orthodox or “traditional” frameworks cannot. For the sake of transparency and clarity, we want to emphasize that this tool is designed to serve the function of guiding school teams through honest and genuine self-evaluation and reflection for iterative growth. This thinking tool is not designed to be an instrument for assessing a school’s practice in teaching computer science content. CSTAR | 1
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Cultivating a mindset for computer science and creative problem solving We want this thinking tool to be helpful when school communities are defining their school-wide and community-oriented goals in computer science and creative problem solving. While this will look different in every school and classroom, there are a few core principles that we have learned from our teachers and school leaders. 1. Everybody In A thriving culture of computer science will need to be sustainable and representative of all the students and caring adults in the school community. Consider assembling a team that will work collaboratively on your school’s computer science efforts. This team does not have to consist exclusively of computer science teachers – nor does it need to consist exclusively of classroom teachers. Think about all the diverse and varied perspectives that the people in your community can bring and enrich your students’ experience in computer science, 2. Think long term Growing a robust CS4All program will be a marathon rather than a sprint, as it requires a reimagining of what roles people should play in participatory learning. You likely already have shared school-wide and district-wide goals. You don’t have to identify an entirely new set of goals geared toward computer science –– build on what you already have. Before looking through the CSTAR, consider identifying one or two goals that you already have for your school, and find a section of the CSTAR that you think most closely aligns with your work. This is not meant as something “extra” on top of all the other responsibilities that teachers and administrators have. 3. Where do you want to get; how do you want to get there? This thinking tool has different ideas that we’ve learned from working with our schools, but computer science education will look different in every school and every classroom. After determining the section(s) of CSTAR that are pertinent to your work, consider dissecting the content in CSTAR until it works for you and your school community. Do the ideas in this thinking tool change how you might approach computer science integration? How well do the elements and components in this thinking tool align with your goals as a school? Recognize that you may be doing things that we have not even thought about, and afford your team an element of grace. 4. Iterate, iterate, iterate After your team uses the rubrics in the CSTAR to determine where you are, you might begin to think about what is working for you and what you would like to add or change to reach your goals. What should your next steps be? That’s up to you and your school community. What are some different ways you can think about the circumstances and conditions of your school? What role could computer science play in your practice? You will have some sort of data after using this thinking tool. How do you want that data to be represented? Communicated? Acted upon? You may not find your answers right away, but this is where an iterative approach is essential. These are four core principles that we have learned about from our work with schools to cultivate creative problem solving as well as computational thinking , computational participation , and computational action . For more on those topics, see page 24. CSTAR | 2
CSTAR “Elements” and “Components” This thinking tool is broken down into five elements that our schools have focused on when establishing or expanding their computer science offerings. These elements are not exhaustive, but we do believe they are essential things to consider. The five elements in the CSTAR are: Leadership | How are we structuring our efforts to value both top- down and bottom-up approaches to computer science integration and expansion? Sustainability & Growth | How are we striking a balance so that our efforts are structured enough to allow for robust longevity, but flexible enough to respond to shifts in our school’s focus? Accessibility & Equity | How are we supporting our community’s diverse perspectives and providing opportunities for everyone to contribute to our computer science learning and growth? Family & Community Engagement | How are we integrating computer science into our community engagement efforts and ensuring that the perspectives of our broader community have a place in our computer science work? Shared Joy | How are we creating an environment that supports the members of our school community when they take intellectual risks and participate in joyful experimentation? Each element is decomposed into smaller components . These components present different ways to think about the larger elements. Below is a chart that lays out the components tied to each element. Element Components Leadership Collaboration · Intentionality · Iteration Sustainability & Growth Computer Science Identity · Monitoring for Progress · Places for Incubation · Partnerships for Learning Accessibility & Equity Equitable Expression · Universal Opportunities for Learning · Deconstructing Barriers to Learning Family & Community Engagement Community Outreach · Community Input · Community Collaboratives Shared Joy Inclusive Spaces · Celebrating Successes (and Failures!) · The Four Ps (Projects, Passion, Peers, and Play) These elements and components are relatively broad because we recognize that there is no blanket approach to computer science education that will work for every student taught by every teacher in every school community. When you are thinking about your own work in computer science education, if you find a helpful element or additional component that is not represented here, do not hesitate to bring your own experience and expertise to your analysis. You know your students and your community best. CSTAR | 3
Reading and using the rubrics For every element and component that we explore, we have provided rubrics that your school community can use to gauge where you are in your CS4All journey. The element / component is joined with a “ big picture ” and four descriptors. Below is a sample rubric that outlines the different parts of the rubrics. Element or Component This box will contain the name of the element or component that the rubric describes The Big Picture This box will contain a guiding question that your team can consider as you self-assess where you are in your computer science journey. Formation This box describes the “formation” stage. This is a way of saying “we are interested in this, but do not yet feel prepared to begin incorporating our learning into our practice.” Adoption This box describes the “adoption” stage. This is a way of saying “we are exploring some different aspects of computer science education to determine what will work for our school community.” Adaptation This box describes the “adaptation” stage. This is a way of saying “we are trying different strategies to form a collective computer science identity.” Transformation This box describes the “transformation” stage. This is a way of saying “our focus is now on refining, sharing, and formalizing our practices in computer science education in different classrooms within our school.” Not all rubrics will have a section on the bottom. This section tells you where else in this document you can look to build upon ideas that you may have. Our rubrics are influenced by a number of different sources. These include the Technology Integration Matrix (TIM) developed by the Florida Center for Instructional Technology at the College of Education (University of South Florida), as well as the Strategic CSforAll Resource & Implementation Planning Tool (SCRIPT) rubrics developed by the CSforAll organization. The descriptors in our rubrics offer a sampling of different indicators that schools may refer to as a shared vocabulary in defining their self assessment, but schools are also free to add other indicators that the rubrics may not account for. The point of these rubrics is not to tell you what direction you “ should ” be moving in, or where your focus “ should ” be directed. Our hope is that this reflective process can empower your school community to design sustainable computer science programs that are reflective of your students and the caring adults in your community. CSTAR | 4
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Elements at-a-glance Below are the rubrics for our five elements. You can use these rubrics to determine what you want your team’s focus to be. Each rubric directs you to the pages in this document that pertain to their respective components. Leadership The Big Picture How are we structuring our efforts to value both top- down and bottom-up approaches to computer science integration and expansion? Formation We are building a computer science team that represents the different strengths of our school community, and we are identifying points where our thinking converges and diverges. Adoption We are outlining what our shared goals are and what methods we want to employ in approaching those goals. We are acquainting ourselves with different ways of thinking, with a focus on cultivating sustainable practices. Adaptation We are concentrating our focus to work on specific goals that we have outlined. We are operating in a design cycle which allows us to iterate on our work and modify our approaches as different needs arise. Transformation We have a shared understanding of how we will define our successes in computer science, the autonomy to determine when our efforts need to adapt to changes in our conditions, and the support of our school community to experiment with different ways to integrate computer science into our daily practice. To explore the leadership components of collaboration, intentionality, and iteration , see pages 8 - 9. Sustainability & Growth The Big Picture How are we striking a balance so that our efforts are structured enough to allow for robust longevity, but flexible enough to respond to shifts in our school’s focus? Formation We are approaching computer science integration using methods that we have already established for our work in other content areas. Adoption As we expand our work in computer science education, we are taking note of how our school community reacts, in order to amplify the benefits of our work. Adaptation We ground our computer science identity in our evolving school culture, and we give our school community the time and space to innovate and experiment in their approaches to computer science education. Transformation Our school culture informs our approach to computer science education as much as our computer science learning informs our understanding of our school culture. To explore the sustainability & growth components of computer science identity, monitoring for progress, places for incubation, and partnerships for learning , see pages 10 - 11. CSTAR | 5
Accessibility & Equity The Big Picture How are we supporting our community’s diverse perspectives and providing opportunities for everyone to contribute to our computer science learning and growth. Formation We make computer science content accessible to our school community by using methods that we have already established for our accessibility work in other content areas. Adoption As we learn about our school community’s outlooks, perspectives, and attitudes to our implementation of computer science, we are building support structures specific to our computer science science, which we can apply at universal levels as well as targeted ones. Adaptation As flexibility and targeted universalism become core features of our approach to equity in computer science, we acknowledge and celebrate the fact that computer science will look different in each classroom. Transformation We ground our systems of support in the belief that everybody can access and fully engage with computer science content and should have the opportunity to build their learning, as well as the understanding that everybody will have different needs in expressing their thinking. The members of our school community advocates for their own needs as well as the needs of others. To explore the accessibility & equity components of equity in expression, universal opportunities for learning, and deconstructing barriers to learning , see pages 12 – 14. Family & Community Engagement The Big Picture How are we integrating computer science into our community engagement efforts and ensuring that the perspectives of our broader community have a place in our computer science work? Formation We are taking stock of our current family and community engagement practices and searching for opportunities for those practices to uniform our computer science work, and for our computer science work to inform our computer science engagement practices. Adoption We are learning the needs and the assets of our broader community and identifying how our work in computer science integration can benefit our broader community. Adaptation We routinely share our successes with our broader community and elicit their feedback on our thinking and strategic planning; we are developing avenues through which our broader community can communicate with one another. Transformation The needs and assets of our community serve as the motivating driver of our work in computer science. We regularly encourage our students and staff to engage in computational action and consider computational solutions to community based concerns. To explore the family & community engagement components of community outreach, community input, and community collaboratives , see pages 15 – 16. CSTAR | 6
Shared Joy The Big Picture How are we cultivating an environment that supports the members of our school community in taking intellectual risks and participating in joyful experimentation? Formation We are grounding our work in the mindset that we want our students to practice when it comes to inclusiveness, celebrating effort, and keeping our work joyful. Adoption We are collaboratively building the frameworks that our school community will use to communicate our thinking with one another and share what is in our work that brings us joy. Adaptation We have built a community and established norms in which our students and staff can find and express joy – not only in the products we create, but in the process of creative computing. Transformation We find creative ways for our students and staff to find and share joy not only in the products that come from our work and the process of creative computing, but also in the sense of belonging to a collective of thinkers and tinkerers. We see ourselves as part of a larger global computing community. To explore the shared joy components of inclusive spaces, celebrating successes (and failures!), and The Four Ps (Projects, Passion, Peers, and Play), see pages 17 – 18. CSTAR | 7
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Leadership As you build your own movement toward CS4All, the unique members of your school community will have a number of different perspectives that should be taken into account. School administrators may have broad considerations as to where computer science fits into long-term school goals. Teachers and staff who work more closely with students may have direct insights as to what different pedagogical approaches work for their students. The students who are learning these computer science skills may want to share their invaluable thoughts about what content speaks to them. Honoring all these layers of leadership will be helpful in enriching your school community’s computer science experience. This thinking tool explores these three components of leadership: collaboration · intentionality · iteration Collaboration The Big Picture How are we creating meaningful leadership roles in our computer science work, encouraging active participation in these roles, and creating an environment where our shared work can flourish? Formation We are starting to form a cohesive team around shared goals in computer science education. This may include things like surveying our staff to learn their interests in computer science education, establishing what our shared priorities are, and learning one another’s unique strengths. Adoption We have found the core of our computer science team, which may include staff who have stepped forward as leaders and/or have an interest in or passion for computer science education. We are determining what roles will support our work and are tailoring our work to our community’s strengths and needs. Adaptation We are finding our footing, bringing our personal and professional interests and skills to the collective table. We are establishing our school’s goals in computer science education and connecting them to our existing school-wide goals. Transformation As a computer science team, we are encouraged to try inventive things to integrate computer science into our daily practice. We have common time to plan, work, and create together. CSTAR | 8
Intentionality The Big Picture How are we developing our computer science efforts in a way that serves our larger goals as a school? Formation We are determining what our goals are in pursuing computer science education, and determining how our computer science goals relate to our greater school goals. Adoption We have identified what we want to do with computer science, and we understand how those goals connect to greater school goals. We are considering what strategies, systems of supports, and partnerships we would need to do our shared work. Adaptation We have honed in on one or a few specific goals in computer science education to concentrate our efforts upon. We have determined how we want to define our work and measure our progress, and what strategies we will employ when incorporating computer science into our different classrooms. Transformation We have a distinct vision of what we want our school to achieve, and have identified clear ways to measure our progression towards CS4All. Our goals in computer science are tied directly to our greater school goals. Iteration The Big Picture How do we ensure that our computer science team has the necessary time, space, and autonomy to reflect on past experiences and iterate on their ideas, plans, and methods? Formation We are familiarizing ourselves with different ways to iterate upon our ideas and work – such as the Engineering Design Cycle. We recognize that iteration requires ongoing dedicating to progressing our ideals. Adoption We are purposefully sharing our learning with one another in a way that we think will lead to practical, manageable, and sustainable growth in different computer science practices. Adaptation We afford our computer science team the time, guidance, and training necessary at the end of each design cycle to collaboratively determine the successes of our work and iterate upon them. This may include reassessing our team’s collective goals. Transformation Our team routinely assesses the success of our efforts and has the autonomy throughout our iterative process to determine whether our computer science education practices are still relevant to our students’ needs. CSTAR | 9
Sustainability & Growth Computer science is a dynamic field. The platforms and practices that we use today may be replaced in just a handful of years. Moreover, comprehensive Pre-kindergarten to 12th grade computer science education is a relatively new field – its “best practices” are still in development. Building your own school-wide culture of computer science will be important in building a strong foundation for your school that will be able to adapt to changes – changes both within the field of computer science education and changes that may occur at the school level, such as shifts in priorities and school goals. This thinking tool explores these four components of sustainability & growth: computer science identity · monitoring for progress ª places for incubation · partnerships for learning Computer Science Identity The Big Picture How are we developing a culture that acknowledges everybody’s potential to fully participate in computer science and be a computer scientist? Formation We are exploring how our already-existing school culture can be positively impacted by our learning around different aspects of computer science education. Adoption We are gathering the viewpoints of our students and staff to define, as a school, what computer science and computational thinking can look like in our particular school environment. Adaptation We are establishing school-wide vocabulary and habits around computational thinking as part of our commitment to the idea that every child has the capacity to fully engage in their computer science education. Transformation We have a school-wide culture that affirms everybody’s potential to fully engage in computer science, and we further encourage each classroom to establish their own culture of computational thinking. Monitoring for Progress The Big Picture How do we keep our focus on iteration and self-reflection while we monitor the progress of our shared work in computer science education? Formation We are keeping track of our progress in computer science education using methods we have already established for our work in other content areas. Adoption We are learning our community’s outlooks, perspectives, attitudes, and reactions to our implementation of computer science education in order to identify what we should measure, interpret, and iterate upon. Adaptation We are building unique monitoring systems for our work in computer science, based on the viewpoints of our school community. Transformation Our team shares an understanding of what metrics we use to monitor our work and why those metrics were chosen. Our metrics do not evaluate teachers or students, but rather let us know how we are doing as a community of learners. CSTAR | 10
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Places for Incubation The Big Picture How are we creating opportunities for our school community to experiment with computer science in supportive environments with lower stakes than a traditional classroom? Formation We are learning from our school community what systems of support we need to construct in order to increase our comfort level with practices in computer science education. We will use this learning to find opportunities to build supportive environments for experimentation and playful learning. Adoption We have determined – and are in the process of organizing – supportive environments (for example, a family engagement event or an out-of-school time program) in which our staff can experiment with exposing our students to practices in computer science education. Adaptation We have established one or more supportive environments in which our community can experiment with instruction pertaining to computer science content and practices. Transformation We are developing times within the school day to create supportive and non-evaluative environments for our school community to demonstrate their knowledge and their computational thinking. Partnerships for Learning The Big Picture How are we building relationships where our school can draw on the experience of a larger computer science community? Formation We are not fully aware of what partnerships are available to us, but are thinking about what kinds of institutions and groups we might be able to partner with. Adoption We are communicating our goals in computer science education broadly in order to form relationships with potential partners who share similar aspirations. Adaptation We are sharing our progress in computer science education with partners with whom we have built relationships, and learning about their work in turn, Transformation We work collaboratively with our partners to review our ideas and plans, develop ways to monitor our progression towards CS4All, and iterate on our structures and routines. Examples of a larger computer science community might include other nearby elementary or high schools, District-level offices, universities, museums, chapters of the Computer Science Teachers Association (CSTA), public libraries, and/or local community-based organizations. CSTAR | 11
Accessibility & Equity The novelty of computer science education in the Prekindergarten to 12th grade space affords us an opportunity to interrogate and resolve inequalities across our educational structures. Teaching computer science in a way that cultivates our students’ unique capabilities requires an intentional rethinking of the desired outcomes of education. To ensure true equity in computer science education, every member of the school community should feel that they have the necessary structures of support to fully and actively participate in their learning and share their thinking with others. On a universal level, this might mean intentionally planning to ensure that all members of the school community are brought into the discussion around goals in school-wide computer science education. On a more targeted level, this may mean identifying what kinds of instructional shifts would best support students who are often left out of computer science. 1 This thinking tool explores three components of accessibility & equity: equitable expression · universal opportunities for learning · deconstructing barriers to learning Equitable Expression The Big Picture How are we ensuring that we are offering a variety of ways for our school community to actively participate in computer science? Formation We are learning about the different ways that computer science can be studied and practiced (such as programming, physical computing, robotics, e-textiles, data analysis, digital arts, etc.), and finding out what appeals to our school community. Adoption We have identified different forms of computer science that we can bring into our practice over time. We afford our staff the time and space to explore computer science in various ways (such as professional development, book groups, and professional learning communities.) Adaptation We have started to formalize the ways in which our school community has different ways to engage in computational thinking, and we work collaboratively to develop structures of support for experimentation in computer science education. Transformation We use our resources and structures of support to engage students in advocating for themselves and others regarding what practices of computer science education are best suited for their goals. 1 For information and resources outlining Targeted Universalism, Liberatory Thinking, and other facets of equity look like within CPS, you can refer to the Chicago Public Schools (CPS) Equity Framework: Creating and Sustaining Equity at the Individual, School, and District Level . CSTAR | 12
Universal Opportunities for Learning The Big Picture How are we giving our school community opportunities to actively participate in learning and applying the concepts and practices of computer science education? Formation We are building a foundation for computer science education by concentrating our work on particular demographics of our school community (such as specific grade levels or content areas). We are seeking ways to sustainably expand computer science to other demographics of our school community. Adoption We are coordinating what we can offer our school community to ensure that everyone has the exposure and opportunity to engage with different aspects of computer science on a continuous basis, to go as far with computer science education as they want to. Adaptation Our staff has various ways to participate in building their knowledge of computer science (such as PDs, PLCs, and book groups), and our students have multiple avenues through which to engage in computer science education (in their homerooms, in enrichment classes, in out-of-school-time programs). Transformation We invite the whole of our school community to have a hand in determining the direction of our collective work in computer science. Our students are presented with access to different avenues through which they can exercise their computational thinking. Deconstructing Barriers to Learning The Big Picture How are we learning about the potential barriers to our community’s participation in computer science education, and modifying our approach to provide opportunities for our students to cultivate their unique gifts? Are we adapting our approach to computer science to meet the needs of our students rather than trying to change our students to meet the needs of our approach to computer science? Formation We recognize that each member of our school community brings unique gifts to our computer science work, and intend to learn about what barriers they may face in expressing their skills, talents, and interests. Adoption We recognize that our personal identities inform our perspectives on computer science. As a community, we are learning how to communicate what we would need in order to flourish. Adaptation We are developing strategies to break down systemic barriers that hinder full participation in computer science. We are making efforts to disrupt the homogeneity of computer science, using what we learn about the values and identities of our community members, and how the different parts of our identities impact how we understand ourselves as computer scientists. Transformation We are sensitive to the different kinds of barriers that members of our school community may face in expressing their skills and talents in computer science, and we have developed strategies to deconstruct these barriers We have provided two sample rubrics on the next page related to deconstructing barriers to learning – one focused supporting English Language Learners, and one focused on supporting Diverse Learners. English Language Learners and Diverse Learners are not the only members of your school community who will benefit from additional supports but we hope these sample rubrics can provide a starting point for your work in deconstructing barriers to learning. CSTAR | 13
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Deconstructing Barriers to Language The Big Picture How are we supporting all of our students in accessing the new language of computer science while also targeting additional systems of support for our students who are English Language Learners? Formation We are supporting our students’ needs in the academic language of computer science – including the needs of our English Language Learners – using strategies that we have developed for other content areas. Adoption We recognize that computer science is a new “language” for all of our students. We are building a shared vocabulary around computer science education to identify what systems of support will help our students – especially students who are learning English – find their place in computer science education. Adaptation We are integrating systems that will support all of our students in cultivating their capacity around technical language while also making sure that our English Language Learners will have additional supports in developing English Language ability. Transformation We create opportunities for students and staff to fully participate in computer science in the language of their comfort, and we explicitly celebrate connections between the languages our students know, the English language, and the language of computer science. Deconstructing Barriers to Accessibility The Big Picture How are we supporting our students in cultivating their different learning modalities while targeting additional supports for our Diverse Learners? Formation We meet the needs and cultivate the abilities of our students by using the methods of accommodation and modifications that we use in other content areas. Adoption We are familiarizing ourselves with the different modalities of computer science (such as programming, the digital arts, data analysis, and physical computing), so that we can use those modalities to accommodate our students’ interests and needs. We may have teachers who are piloting integration of these modalities with their students in an iterative way. Adaptation We give our school community the flexibility to determine how we implement the different modalities of computer science, and we afford our students flexibility in expressing their learning through the means of engagement that work best for them. Transformation Our identity as a community of computer scientists is tied to our drive to afford students access to the resources and structures of support that are necessary for them to advocate for their needs in communicating and expressing their participation in computer science. CSTAR | 14
Family & Community Engagement Computational Participation is a way of engaging with computer science that focuses on how we go about “solving problems with others and learning about the cultural and social nature of human behavior through the concepts, practices, and perspectives of computer science.” 2 A school community is broader than the physical building and includes the students’ families, local community organizations, and local institutions. We have seen computer science thrive at schools most when the views of and priorities of the broader school community are taken to heart when establishing school-wide computer science work and learning, and when the broader school community has ways to participate in celebrating this new field of study. This thinking tool explore three components of family & community engagement: community outreach · community input · community collaboratives Community Outreach The Big Picture How are we communicating our work in computer science integration to our school community that exists beyond our school building? Formation We are starting to build partnerships with members of our broader community. We are identifying our points of contact and determining what avenues are available to us for communicating our school’s efforts and successes. Adoption We are coordinating our work with the partners in our community. We are learning what developments they would like to be kept informed about, and learning how they can be involved in our school’s work in computer science education. Adaptation We regularly share our thinking, our plans, and our strides through CS4All with our broader community, and we are tailoring our methods of communication in a way that works for our community. Transformation We are situating ourselves as a community hub . We are coordinating with our broader community to assist in building relationships where they were not otherwise present. (For example: we are establishing ways for our families to communicate directly with our local organizations). 2 Kafai, Yasmin B., and Quinn Burke. Connected Code: Why Children Need to Learn Programming . Cambridge, MA.: The MIT Press, 2016: 128. CSTAR | 15
Community Input The Big Picture How are we keeping the priorities, needs, and assets of our broader school community in mind when designing and orienting our school-wide computer science work? Formation We specifically and intentionally incorporate what we know are the needs of our broader community when we determine our school-wide goals in computer science education. Adoption We are deliberately learning from our community what their needs and assets are, and, based on that feedback, identifying what position we are poised to play in community engagement and collaboration. Adaptation We are taking the needs and assets that our broader community communicates to us and incorporating those needs and assets into our process of planning computer science experiences for our students.. Transformation We integrate our community’s needs and assets into our work and encourage our students to engage in finding computational solutions to community-based concerns. Community Collaboratives The Big Picture How are we providing opportunities for our broader community to participate in the kinds of learning that our students and staff are engaging in? Formation We are evaluating our current approaches to community engagement and finding opportunities where our established engagement practices and our developing computer science identity and culture can inform and influence one another. Adoption We are organizing “one-off” events where our students can show their learning to their families and our broader school community. We may also be exploring how we can act as a hub for our broader school community to engage in their own journey around learning computer science (such as parent workshops and open houses). Adaptation We are identifying the key elements of our computer-science-oriented community engagement events, with the intention to make them regular occurrences and deepen our collaborative energy with our community. Transformation The feedback that we receive from our broader school community directly influences and shapes the workshops and events that we organize for our broader community. Resources which may be helpful in planning out family and community engagement events include the Family Creative Learning Facilitator Guide written and designed by Ricarose Roque and Saskia Leggett at the University of Colorado Boulder and the Virtual Family Creative Coding Night Facilitation Guide , written by the CPS Computer Science Department in collaboration with the Scratch Foundation. CSTAR | 16
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Shared Joy To build toward CS4All is to build toward a thorough, equitable, and comprehensive computer science education for every student – but it is important to retain the vital and intangible element of playful learning that makes computer science education the creative and collaborative experience that is. The iterative process that is so central to computer science relies on repeated attempts and, yes, repeated failure. You cannot make progress on a project if you do not learn from what went right and what went wrong! How do we create the requisite warm and inviting places rich with joy and collaboration (and failure!) to foster joyful conditions for our students? This thinking tool explores three components of shared joy: inclusive spaces · celebrating successes (and failures!) · the Four Ps (Projects, Passion, Peers, and Play) Inclusive Spaces The Big Picture How does our school environment work to provide a warm and inviting space for exploration in computer science? Formation We are bringing together our instructional practices, our learning in computer science, and our social emotional learning practices to develop supportive atmospheres that reinforce our encouragement for experimentation, tinkering, and conflict resolution. Adoption Our norms around inclusive spaces guide the organization of our computer science environments (both physical spaces such as classrooms and labs, as well as the metaphorical environments that come with building a community of learners). Adaptation We recognize the important role that technology plays in our students’ lives and we take opportunities to explicitly teach digital citizenship and interrogate inequalities in computer science in a way that emphasizes resolution. Transformation We provide our school community with the resources and the systems of support necessary to apply their learning in digital citizenship to conflicts that may arise in their day-to-day lives. CSTAR | 17
Celebrating Successes (and Failures!) The Big Picture How are we creating opportunities to recognize and celebrate the work of our school community, and affording our teachers the opportunity to learn from one another. Formation We actively practice celebrating one another’s successes in integrating computer science into their practice. This may include celebrating our efforts and successes in staff meetings and school-wide gatherings. Adoption We are establishing practices our students can use to share their thinking and their work (such as discussion stems based in the language of computer science). Adaptation We are experimenting with ways to prominently display our school community’s work to our school and broader community. This may include hosting family creative coding nights or exhibiting students’ work in common areas. Transformation We recognize failed efforts as integral to success, and appreciate steady growth as valid growth. We ensure that our celebrations acknowledge “failed” efforts – and, more importantly, the learning that comes from them. The Four Ps (Projects, Passion, Peers, and Play) The Big Picture How are we incorporating the Four Ps into our students’ computer science experience? Formation We incorporate the Four Ps into our own leadership processes so that our work in computer science education is guided by inventive projects, individual passions, peer-to-peer collaboration, and joyful learning through play. Adoption We are focusing on sustainability by bringing one or two of the Four Ps into our classrooms at a time, so that we can understand how our students’ attitudes toward computer science develop. Adaptation We transfer ownership of the work to our students – with our staff acting as facilitators in their learning. In the spirit of the Ten Tips for Learners, written by children at the Boston Museum of Science, we give our students the tools to “create your own learning tips.” 3 Transformation We use a design cycle (imagine, plan, create, experiment, improve, ask) to look for ways to expand our practice in the Four Ps to spaces outside of the classroom, such as common areas that our school community may use. 3 Resnik, Mitchel. Lifelong Kindergarten: Cultivating Creativity Through Projects, Passion, Peers, and Play . Cambridge, MA.: The MIT Press, 2017: 167. CSTAR | 18
Common Threads Regardless of which element your computer science team chooses to focus on – whether it’s leadership, accessibility & equity, or shared joy – there are common threads of thought that run throughout this document. This section is an attempt to be a thought partner for these big overarching topics. Who is computer science “for”? Computer science takes many forms. Decomposing large problems into manageable ones is an aspect of computer science. Designing conceptual and algorithmic solutions to everyday problems is an aspect of computer science. Creating programs to perform complex calculations is an aspect of computer science. Analyzing data, strengthening privacy and security protocols which ensure usability, automating repetitive tasks, creating human-oriented interfaces – these are all aspects of computer science. These all fit under the umbrella of computer science because computer science is not a series of steps to be memorized, but rather a way of thinking about big problems. And since computer science is a way of thinking about problems we all have, computer science is for everyone. What does this mean in the context of your school? How can you ensure that access to a thorough and comprehensive system of computer science education is inclusive of everyone in your school community? How do you, as a team, ensure that the direction of computer science at your school is collaborative and informed by all the rich ideas that exist within your building and beyond it? New teachers as well as veteran teachers? SECAs and paraprofessionals? Principals and students? Where does computer science “fit”? Just as computer science exists in many forms, there are many ways to approach computer science education so that it works for your school and your students. Computer science can exist as a standalone course for every student. It can also be used as an integrated practice, where key concepts of computer science are taught alongside other content areas such as Mathematics or English Language Arts. We have seen schools experiment with offering computer science as an opt-in “elective” course or as an out-of-school-time program to foster a more experimental environment before bringing it into the classroom. Think about the way you want to bring computer science into your practice – what implications does it have for equity and accessibility in your work? If you offer computer science as an out-of-school-time program, how can you accommodate students who many have an interest in computer science but may not have the ability to be present before or after school? How can you accommodate your students who are interested in one aspect of computer science (such as data analysis) as well as your students who are interested in something else (such as digital media)? Keeping the joy in learning. There is a lot of room for play in education. In mathematics, we regularly encourage our students to “play with the numbers” when a shift in perspective allows for a reinvigorated understanding of how different concepts affect one another, and – in this play – find the joy in mathematics. To teach writing – especially creative writing – is to encourage students to “play with the language” CSTAR | 19
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
and communicate ordinary things in extraordinary ways, and find the joy that comes in self-expression. Computer science education, too, allows for – and encourages – different kinds of playful learning, not just in the way of a “Fun Friday,” but in a way that emphasizes the joy that comes from creating something. More importantly, computer science education easily lends itself to exploring the joy that comes from working together, because so much of computer science has to do with how we interact with one another in our current technological landscape. It is a given that you will keep your students in mind when establishing or expanding your computer science offerings. We hope that the process of collectively reflecting on what it means to participate in computer science will further bolster your own joy in working as a team. CS4All as a continuous journey. A truly equitable, thorough, and comprehensive program of computer science education that responds to the needs and aspirations of each member of a school community is not something that can be achieved in a day, or in a semester, or over the course of an academic year. Writing about previous movements in computer science and technology education, Jane Margolis points out that: In this country, K-12 schools and educational systems are among the institutions most significantly affected by technology, and they are also well positioned to directly address these inequalities. Yet K-12 school districts still succumb to the pressure that derives from the myth of technology as “the great equalized,” as they have paid more attention to populating schools with the latest tools than to support engaging and rigorous pathways of computer science for all students. 4 We learned from our school not to see “CS4All” as a static designation, but as a flexible process and continuous journey of learning that will look different at every school. It may even look different each year at the same school. To study computer science is to study how we relate to one another through our digital environment – and because our digital environment is always changing, so should our approaches to computer science education. The path to CS4All is one what will require intentional planning, iteration after successes and failures, and a lot of creativity. Do not get discouraged if it does not happen right away! 4 Margolis, Jane, Kimberly Nao, Jennifer Jellison Holme, Rachel Estrella. Stuck in the Shallow End: Education, Race, and Computing . Cambridge, MA.: The MIT Press, 2017: xi . CSTAR | 20
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Last, but not Least This final section contains some information and resources which you may find helpful if you want to take a deeper dive into the thinking that went into creating the CSTAR thinking tool. About the Computer Science Department The Computer Science Department at Chicago Public Schools supports school staff, teachers, administrators, and students in their journey to bring computer science into their classrooms in a way that cultivates and develops the unique gifts of every student. With the ever-increasing role that new and different technologies play in our lives, and with the depth and breadth of skills and knowledge required to fully access these technologies, the question of who has access to a thorough computer science education is, to us, a question of social justice. Our work is guided by equity, inquiry, and computer science content. Our focus on equity directly impacts our efforts to provide meaningful educational opportunities to teachers, students, and communities who typically encounter barriers to accessing computer science and computer science education. Our focus on inquiry pushes us to engage students with questions designed to stimulate their curiosity about how our modern world works and came to be, rather than delivering prepackaged lectures. Our focus on computer science content lends itself to a holistic approach to computer science that goes beyond computer literacy and programming, and creates a welcoming environment for our students to engage with the opportunities of our digital and technological society. The dedicated teachers and school leaders we work with, the amazing students we support, and the innovating partners we collaborate with make it possible for us to help our young people become global citizens who understand the ubiquity of computing and use their knowledge to join the ranks of those who embrace technology. Our students can revolutionize their communities and have a direct hand in shaping the world in which they want to live. CSTAR | 21
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
Our case for Computer Science Education In the elementary school space, computer science – like science, civics, or the arts – is in a funny position. These are fields with few detractors – is there anyone who works in education who will argue that they are not important topics for our students to study? But these are also the fields that are often relegated to the category of subjects that “would be nice to teach, if only we had the time.” They are the content areas that teachers often have to find creative ways to “sneak” into the school day, and they are fields that frequently require new justification as to why they should be taught. The case for computer science is often tied to its stature in the labor market – the increasing career prospects it offers and the utility of computational thinking to any potential occupation. Those arguments do , in fact, carry water. Careers in, for example, computer and information research 5 and software development 6 have grown “much faster than average” and are projected to continue to do so. Labor markets change, however, and the demand for different skills ebbs and flows. So the question is: beyond the current labor market, why should we teach computer science to our young people? 1: Computer Science will only continue to grow in importance in our students’ lives. Computer science – and, specifically, the thinking it engenders – is and will continue to be an essential interdisciplinary tool in tackling the problems our students will face in their futures. It is difficult to think up a single occupation or field of study that is not in some way affected by the advances in computer science. Recognizing the impact that computing and computational thinking will have on all kinds of fields of knowledge, institutions of higher learning are forming CS + X programs. These programs include: the CS + Chemistry, CS + Linguistics, and CS + Music programs at the University of Illinois at Urbana Champaign and Northwestern University , the Digital Humanities minor at Stanford University , and the Digital Studies program at The University of Chicago Even if we do not consider the learning that happens in colleges and universities, our young people will increasingly be affected by advances in computer science. In her research, Jane Margolis summarizes the place of computer science in interdisciplinary work: Occupations, industries, and undertakings as diverse as HIV and Influenza research, air safety, psychological inquiry, the elimination of world hunger, studies of the world’s climate, and the Human Genome Project, just to name a few, would all be crippled without the benefit of computer science. On a grand scale, computer science is transforming knowledge and the scientific questions that can be investigated. It is not just science that is being transformed. In the creative arts, the changes brought on by computation are also sweeping. 7 Not only will a thorough understanding of computer science concepts and principles help our students become active participants in the 21st century, but computer science is and will 7 Margolis, 7. 6 Bureau of Labor Statistics, U. S. Department of Labor, Occupational Outlook Handbook , Software Developers, at https://www.bls.gov/ooh/computer-and-information-technology/software-developers.htm (accessed May 11, 2021). 5 Bureau of Labor Statistics, U. S. Department of Labor, Occupational Outlook Handbook , Computer and Information Research Scientists, at https://www.bls.gov/ooh/computer-and-information-technology/computer-and-information-research-scientists.htm (accessed May 14, 2021). CSTAR | 22
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
continue to be a vital avenue through which we can help our young people understand why our world is the way it is, how it impacts us all, and how we can work together to influence its development. 2: We can use computer science education to interrogate our current practices in education While computer science is a far-reaching and impactful field of study, it is still relatively new in the arena of Prekindergarten to 12th grade education. Unlike more established content areas such as Mathematics or English Language Arts, the “best practices” in teaching computer science are still very much in development. What we have learned from our teachers is that the things which constitute “good teaching” in computer science are the same things that constitute “good teaching” across the board – namely, a focus on empowering students – but the novelty of computer science education affords us a lens through which to assess our practices in education more broadly. We know already that there exist significant opportunity gaps within and among school districts. We know, too, that to teach a new field without interrogating and resolving the contradictions in our existing ones only replicates the flaws in the new field. Do we want to replicate the inequalities that exist in Prekindergarten to 12th grade education into computer science – to have our young people internalize their position as “not a computer science person” the way we often hear it stated that they are “just not math people”? Or do we want to place equity at the center of our computer science work? Given the increasingly influential role that computer science will continue to have in our world and our students’ worlds, those who are locked out from fully participating in computer science education are essentially locked out from participating in our rapidly changing world. 3: By learning how our technological environment impacts our human interaction, we can learn about ourselves and about one another It is difficult to overstate the impact that these fields – computer science, civics, the arts – currently have and will continue to have on our students. We teach the sciences so that our students can come to understand the workings of the natural world; we teach civics and history to prepare them to engage with one another in communities; we teach the arts so that our students can share their inner worlds with one another. What do we teach computer science for? Historian Ira Berlin argues that “history is not about the past … history is about the arguments we have about the past. Because it is about arguments we have about the past, it is really about us, our times, and our problems.” 8 In the same way, we argue that computer science is not about computers; it’s about us – how we relate to one another through the medium of our technologies, how we share our thinking with one another in all of our wonderful ways. Computer science is often framed with the context of “how can we use the technology that we have to achieve the things we want to achieve?” But to study computer science is to become familiar with the systems that surround us all, digital or otherwise. What we want to ask, therefore, is “how do we – and how should we – interact with our technological environment and our digital world, and how do we use our technological environment to create a fairer and more equitable society that works for everyone?” 8 Berlin, Ira. The Long Emancipation: The Demise of Slavery in the United States . Cambridge, MA: Harvard University Press, 2015: 1. CSTAR | 23
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
CS4All: Teaching computer science for equity and inquiry We truly want this tool to be helpful – something that schools can use when developing their own unique paths toward offering a thorough and comprehensive program of computer science education for all their students. We want to work with schools on the question of “how do we – and how should we – interact with one another in our technological environment?” To that end, there are a few key ideas that we want to investigate. These key ideas are computational thinking, computational participation, and computational action . Computational Thinking has to do with “solving problems, designing systems, and understanding human behavior, by drawing on the concepts fundamental to computer science.” 9 When somebody decomposes a large problem into smaller ones, or abstracts the solution to one problem so that it can be used to solve a different one, they are engaging in computational thinking. Computational Participation expands on the framework of computational thinking, and focuses on personal expression and societal participation. It has to do with how we engage in “solving problems with others, and learning about the cultural and social nature of human behavior through the concepts, practices, and perspectives of computer science.” 10 When somebody is empowered to engage in self-expression in a community of problem solvers, they are actively engaging in computational participation. Computational Action pulls the practices of computational computer science into the material world. Computational action proposes that “while learning about computing, young people should have the opportunity to do computing in ways that have direct impact on their lives and their communities.” 11 When somebody identifies a problem in their community, identifies what appropriate tools are available to them, and works with others to develop community-oriented solutions , they are engaging in computational action. Computational thinking, computational participation, and computational action are not links in a chain of progression – you don’t “graduate” to computational action and abandon what you learned about computational thinking. These are all essential parts of what we mean when we say computer science and computer science education . What does it mean to teach computer science in a way that is equitable to all students – to ensure that all students are supported in exploring their computational thinking; that all students’ approaches to computational participation are welcomed; that all students are encouraged to take computational action to solve community-based issues? What does it really mean to offer CS4All? Broadly, CSForAll is a movement to empower all students from kindergarten to high school to “learn computer science and be equipped with the computational thinking skills they need to be creators in the digital economy, not just consumers, and to be active citizens in our technology-driven world.” The mission of the CSForAll organization is to “make high-quality computer science an integral part of the educational experience of all K-12 students and teachers and to support pathways to college and career success.” 11 Tissenbaum, Mike, Josh Sheldon, and Hal Abelson. “From Computational Thinking to Computational Action.” Communications of the ACM 62, no. 3 . March 2019: 34 – 36. 10 Kafai, Connected Code , 128. 9 Wing, Jeanette M. “Computational Thinking.” Communications of the ACM 49, no. 3 . March, 2006: 33 - 35. CSTAR | 24
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
What does this mean in the context of Chicago Public Schools, the birthplace of CS4All? New and different technologies play an ever-increasing role in our lives. They require an intensive depth and breadth of new skills and forms of knowledge to fully access. Locking students out from learning to navigate these new systems essentially locks them out from understanding why our technology-driven world is the way it is and what can be done to make sure it is equitable and just. For that reason, the matter of who has access to programs of computer science education is a matter of pedagogical and social justice. CS4All means that our work is to ensure that every child has the early exposure to computer science necessary to take ownership of the technologies of our digital environment. Entire communities have been implicitly or explicitly shut out from participating in computer science on the basis of race, sex, gender identity, where they live, or how much money and social capital their families have. Our work is to fight against that. This does not mean that all of our students will want to become computer scientists – and that is ok! It means that it is on us to give all of our students what they need to understand and fully participate in the workings of our technological world, and allow them to take computer science as far as they want to, regardless of their ultimate occupation or field of study. The thinking skills that come out of computer science have the potential to build true communities of thinkers and tinkerers who can revolutionize their communities and build the world in which they want to live – to reinterpret old ways of thinking and work collaboratively to create new ones. That is what we owe to our young people. CSTAR | 25
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help
References and Resources Throughout the CSTAR document, we mentioned (and linked to) different resources that inspired some of our thinking. Here is a collection of the resources that we referenced and linked to, as well as a few that we did not. Referenced Books and Articles Kafai, Yasmin B., and Quinn, Burke. Connected Code: Why Children Need to Learn Programming . Cambridge, MA.: The MIT Press, 2016, Margolis, Jane, Kimberly Nao, Jennifer Jellison Holme, Rachel Estrella. Stuck in the Shallow End: Education, Race, and Computing . Cambridge, MA.: The MIT Press, 2017. Resnik, Mitchel. Lifelong Kindergarten: Cultivating Creativity Through Projects, Passion, Peers, and Play . Cambridge, MA.: The MIT Press, 2018. Tissenbaum, Mike, Josh Sheldon, and Hal Abelson. “From Computational Thinking to Computational Action.” Communications of the ACM 62, no. 3 : (March 2019) 34 – 36. Wing, Jeanette M. “Computational Thinking.” Communications of the ACM 49, no. 3 . (March, 2006): 33 – 35. Referenced Thinking Tools and Frameworks Chicago Public Schools. Chicago Public Schools (CPS) Equity Framework: Creating and Sustaining Equity at the Individual, School, and District Level . Chicago, Illinois: August, 2020. Chicago Public Schools Computer Science Department, and Scratch Foundation. Virtual Family Creative Coding Night: Facilitation Guide . Chicago, IL. and Boston, MA. Retrieved from http://bit.ly/virtualcreativecoding CSforAll. The SCRIPT: Strategic CSforAll Resource & Implementation Planning Tool for School Districts. Retrieved from https://drive.google.com/file/d/1J-OCxgX_yqcluXlOAKWnh0T6GJj8t3HA Florida Center for Instructional Technology. The Technology Integration Matrix . Retrieved from http://mytechmatrix.org Roque, Ricarose, and Saskia Leggett. Family Creative Learning Facilitator Guide . Boulder, CO. Retrieved from http://familycreativelearning.org/guide/FCLGuide-20170628.pdf Additional Resources Flapan, J., Hadad R., Shorall, C., & Twarek, B. (2020). CS Equity Guide: A K-12 education leader’s guide to designing, scaling, and sustaining equitable computer science in California . Los Angeles, California: University of California, Los Angeles. Moeller, Babette, and Heather Sherwood. The CT Integration Framework. New York, NY: Center for Children and Technology, Education Development Center. Retrieved from https://drive.google.com/drive/folders/12Si1kHwlqXELoBgD2Zrm2olTkqiRhgpy CSTAR | 26
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help