<?xml version="1.0"?>
<rss version="2.0">
   <channel>
      <title>Leadership PLC - EDI: Chapters 1-3 (Oct.-Nov. 2016) by Myrlene Pierre</title>
      <link>https://padlet.com/mpierre1/nw95d1aco577</link>
      <description>(1) Read Chapters 1-3 
(2) Activity: Bring Classroom Walkthrough Notes
(3) Respond to the following questions:
-What elements of EDI are strongest in your school?
(refer to design/delivery components on pp. 13-14)
-What forms of Checking for Understanding/Formative Assessment
have you noticed during the first month of school?
-At your school, what would be a key area needing refinement?
Discussion: How can we support EDI elements at school sites?
</description>
      <language>en-us</language>
      <pubDate>2016-10-07 00:34:35 UTC</pubDate>
      <lastBuildDate>2023-03-03 17:19:39 UTC</lastBuildDate>
      <webMaster>hello@padlet.com</webMaster>
      <image>
         <url></url>
      </image>
      <item>
         <title>Exit Slips (Sean Delgado, San Antonio High School)</title>
         <author></author>
         <link>https://padlet.com/mpierre1/nw95d1aco577/wish/129163387</link>
         <description><![CDATA[<div>This is probably no shocker to everyone, but this is a great CFU activity.  The lesson was designed to answer the question if viruses are living beings or not, and involved thinking maps, close readings, and a culminating writing activity.  To conclude the lesson, Community Day School had to post these exit slips before they left.  It was clear that 80% understood the lesson objectives, and about 20% did not.  We could tell based off the level of complexity in the responses. <br><br>Below are samples of the door, and two examples of the varying degrees of understanding.</div>]]></description>
         <enclosure url="https://padletuploads.blob.core.windows.net/aws/95901394/48d922b566116dc34f9505d6f5891b6a/CFU_Virus.jpg" />
         <pubDate>2016-10-07 15:38:10 UTC</pubDate>
         <guid>https://padlet.com/mpierre1/nw95d1aco577/wish/129163387</guid>
      </item>
   </channel>
</rss>
