Monday, August 7, 2017

Lindbergh Learning Team - Beginning a Journey Together

Last Wednesday, the Lindbergh Learning Team met to plan for a strong feedback loop of curriculum, instruction, and assessment.  This team's role will be to develop a path to ensure that Lindbergh's grading practices match its curriculum.  It's a thorny task, one that begins with philosophical discussions about the purpose of grading....

Swap Talk:  Share a grading scenario with your partner and get their input on solving the problem.
Swap Talk:  Switch scenarios and find a new partner for a new perspective.
And, continues with creative problem solving. 

The Problem:  Cell Phone Distractions During Meetings

Working Collaboratively to Solve the Problem
The Solutions:  

Place your phone inside the provided doors, and when appropriate, the "garage doors" open to provide access to your device.

Jam the access with this lovely pet.

Use your device at the wrong time, and an explosion of hot coffee, whipped cream, or confetti may send a reminder to everyone that to stay off their phones.
 The Presentations:
Sell your idea to the audience...which will be the best?

Like the above problem-solving activity, the Lindbergh Learning Team knows that grading practices are not a "one-solution" task.  It's up to us to determine what Lindbergh needs and how to support it.  As the year progresses, we'll continue our study of Charting a Course to Standards-Based Grading and work in small groups to further our knowledge:

  • Professional Development - What does this team need and how does it further the learning at the building level?
  • Research - What does the research say about these practices?  Nationally and locally, where has it worked well and where has it failed?  How do we learn from the work of others?
  • Stakeholders - What's the input from parents and students?  How do we coordinate with student information systems to ensure success?
  • Current Grading Practices - Where are we currently as a district and what do teachers need to be supported in any changes that may arise?






No comments:

Post a Comment