Teaching – OA Lesson Plan Development

I’m currently collaborating on tweaking/developing a lesson plan and corresponding curriculum to teach Washington high school students about the chemistry involved in ocean acidification.

This is a project that’s already been in the works and I’m being brought in to assist (or, take over?) with the development. I’m pretty interested and excited by this. The reason for my excitement is that I was in the secondary education program to become a certified secondary education teacher while I was in graduate school. So, this project lets me apply the knowledge I garnered about teaching science during that time.

The current state of the project has a lab protocol, but no real lesson plan for the teachers to utilize. The lab protocol, in my view, is a bit too dense for high schoolers to digest and is a bit too much of “do this, write down the number: that’s ocean acidification!” It currently lacks an important element of science pedagogy: discovery. My goals are to tweak the protocol in such a fashion that it is more engaging and, possibly, hypothesis-(i.e. discovery) driven. This type of teaching has been shown to greatly improve retention and help improve/develop critical thinking skills.

The lesson plan should have sufficient information for teachers to decide if the lesson is appropriate for them to teach (e.g. which Washington state standards are addressed, what learning level(s) does the lesson require, what materials/supplies are needed, etc.), if they have enough time to conduct the lesson, and if they have ample understanding of the topic to feel comfortable teaching it.

I’ve put this project on GitHub. It allows for active collaboration on projects. Although there are some hurdles for those collaborators who have not used the service before, I think there are some good organizational benefits that are worth dealing with the initial headaches that might come for beginning GitHub users.

One benefit to developing this project on GitHub is that all changes are tracked and a description of the changes are required when they are made. This makes it relatively to see what changes were made, by who, and when. Although using something like Google Docs also automatically tracks changes, it does not allow the ability to provide a comment when changes are made. Because of this, it’s not always clear why the change was made in the first place.

An additional benefit, and this is the main reason I think it’s best to develop this project on GitHub, is the Issues tracker (see screenshot):

 

The Issues section allows for targeted discussion of the project and eliminates the volleys of email that often happen on collaborative projects. It will keep all discussions about this project in a single location and won’t require exhaustive searches of emails that easily get buried during a work week. Additionally, the discussions can remain focused on specific topics without getting lost within a emails attempting to broach multiple topics at once.

 

Leave a Reply

Your email address will not be published. Required fields are marked *


e.g. 0000-0002-7299-680X

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>