Context
As I read posts from fellow COETAIL bloggers through both of these first two courses, it reinforces what I already knew about my school with regard to technology integration. At my school, we do not have 1-to-1 computing and a proposed BYOD trial for Grade 9 students was rejected by the company that runs our school. Our access to computers is limited to two computer labs of twenty computers each. This is for a school of 750+ students in Grades 6-9. The computers are adequate to the task even though they are a generation or two old. (They are given to the school when the company replaces the ones used by engineers, etc.)
Most of our students have access to the web at home, and via smart phones, iPads, and other devices. We are a prime example of “disconnect at the school door” that we have read about in our COETAIL courses thus far.
Many digital tools are also blocked by the company – Google Apps and Google Earth are two examples that are particularly frustrating for a sixth grade geography teacher. Cloud computing in general is not possible as the company blocks these sites in the interest of corporate security. Google Docs is available only at home. The use of Nings, blogs, Facebook, etc. with our students is not allowed. I went through a two year process to get a wiki approved for use only in my sixth grade class. It is still up and running, but I signed agreements with the company that I would reveal its URL only to my current students and parents, create a new, separate wiki every year, and never identify the name or location of the school. I would also not upload any documents that could, in turn be downloaded outside our little “walled garden.”
In sum, I believe that limited access to computers at school, combined with the corporate and school polices that prohibit the use of many digital tools and social media discourages many members of our school staff from using technology with our kids. Sure, we have Promethean boards in our classroom, which is great. But most often, we are the primary users and students are mere consumers.
I heard Ian Jukes give a keynote presentation at the NESA Teachers’ Conference in Bangkok in 2000. His explanation for what was to become his blog – the Committed Sardine - struck a chord with me then, and still does today. My school is his proverbial slow-turning whale. But with all of that as context – I am an optimist, and I believe we have the collegial spirit and desire to push, pull, and prod our school towards where we would like to be in terms of technology – for students and staff. We are beginning to feel this whale turn. We are not a school of sardines yet – but maybe…
Our AUP…?
Our district does not have a AUP that is exclusively for the school and our students. Again, I wonder if it is our lagging behind in technology use that has delayed our development of an AUP. All users of the internet in the company sign a internet use agreement, and our kids need a parent signature on that same form in order to use the internet at school.
We do have a digital literacy curriculum component to all of our other curriculum documents. Therein are standards around the Big Idea of Digital Citizenship, but in the main they are simply “cite sources appropriately.” In addition, we have a Fair Use and Copyright Guidelines poster displayed in both computer labs.
The Lead Up
For this project I worked mainly with the technology facilitator (a new position at our school in the last three years) to begin to develop acceptable use guidelines. In the course of our readings and discussions over coffee and doughnuts, I ran across a blog post on Edutopia by Steven Anderson. He writes about his work at the Kimmel Farm School in North Carolina and their desire to create a Best Practices for Social Media document to guide and support teachers who were reluctant to bring social media tools into their classroom practice. This was a part of their school improvement plan. They wanted to “create an environment where faculty are educated and can educate students in the 21st century literacies.” I was really excited about that their focus was going to be not only on the students, to work with faculty as well. That is part of what need to do at my school as well. I was thinking – could we use this type of document to not only guide students, but encourage teachers, and begin to change our school culture with regard to technology.
Developing This Project
We looked at several examples of Acceptable Use Policies and read articles with suggestions about developing a AUP. One that was useful in providing a framework was this page on the Education World website. Ultimately, we used (most of) this framework in our final product, and so we included a preamble/philosophy as suggested.
We wanted to create a simple document of not more than one page, front and back. Small steps. We also wanted to keep statements short and easy to understand. And we wanted to write as many of them as possible in “positive” terms – to write them as “do this” and not as “don’t do that.” We chose not to differentiate between an acceptable uses and unacceptable uses sections, as suggested on the Education World site. We chose instead to keep the main ideas intact, and place both acceptable and unacceptable uses descriptions together for the sake of clarity for younger middle school students.
Our curriculum documents use Essential Questions / Big Ideas as guide to guide standards development, and we incorporated this into our AUP. We choose to use the Big Idea – “What are the responsibilities for users of technology at SAS?” Thus we decided to call ours a Responsible Uses Agreement (RUA) as opposed to an AUP.
We also decided to try to connect to our school code – which is PRIDE. The R is for respect, the I is for integrity, and the D is for diversity. We thought we could connect to those easily. Our initial thoughts fell to these ideas, which we then expanded on:
- Respect – respect intellectual property and copyright, respect SAS network guidelines
- Integrity – protect privacy, be honest
- Diversity – recognize and respect the cultural diversity within our school
And here it is….
Here is our final product, built literally from scratch, by two guys with an interest and just enough knowledge to be dangerous. We recognize that there is much we may not even realize needs to be included. But it is our starting point. Read it with kindness…
Our next step may be to develop this and tie it to a revised proposal for a BYOD policy that may be approved by the company hierarchy.
Let’s get this whale turning…






