A huge decision has been made to upgrade from SharePoint 2007 to SharePoint 2010. These SharePoint Diaries are meant to help me flesh out some ideas and to help others who may be going through (or about to go through) a similar transition.
Now that you know what we’re starting from, it’s time to start thinking about where we want to be.
To start, I asked the Middle School/High School teachers to fill out a shared Google Doc, answering the following three questions:
- What functions of the current portal do you use or ask/expect your students to use most often?
- Ideally, what would you like to be able to do with your students that cannot currently do easily? (I also asked them to keep in mind the work we did earlier on our Tech and Learning Plan to help guide them.)
- Any other comments?
The first question was to ensure that we don’t discard something that teachers find useful. With the second question, I purposefully avoided phrasing the question in terms of “What do you want SharePoint to do?” and instead wanted teachers to focus on the bigger picture ideas embodied in the NETS, such as collaborate, communicate, and create. The third question was included mostly to help keep the first two questions on track!
Once teachers had a chance to voice their thoughts, I asked for volunteers to come together face-to-face and discuss them in more detail, sort of like a focus group. In total, there were 5 teachers present and myself. I shared the objectives of the meeting that I had identified prior to the meeting:
- To consolidate the general feelings of the MSHS staff with respect to their wishes for the new portal.
- To attempt to re-imagine what our school portal will/can be used for.
- To offer suggestions and concrete examples as to what the portal could/should/might look like on August 1, 2011.
To help us meet those objectives, I framed them in three questions which I will include, along with the collated notes, in their entirety below.
What I found, or rather what was reinforced, through this process were some major takeaways:
- Our SharePoint implementation must be student-centered. As you can probably tell from my previous post, it currently is not. Students need spaces and permissions to create and collaborate. They need ownership and control and an audience.
- Whether through SharePoint or some other means, we must address the issue of portfolios.
- Teachers are concerned about the proprietary nature of SharePoint, both for themselves and for the students. Can the work that they put into SharePoint be exported? Can it then be imported into something else? Our community is highly transient and this is important. Portability is an issue.
- In order to teach differently, we need the tools/access/flexibility to do so.
This, of course, is only the start. Now that we have an idea of what is needed/wanted, the question becomes: how can we meet these needs/wants? Environments matter. And currently, our virtual learning environment is, to some extent, shaping how we teach because of its limitations.
Later this week the Redesign Task Force will be meeting to discuss the feedback given by teachers across the school and to come up with some ideas of what that might look like. What can we do to create a learning environment that allows us to teach the way that we would like to teach? That allows us to fulfill our mission statement of encouraging “independent lifelong learners”?
I anticipate that this is also where we will begin discussing the different add-ons or modules that have been developed for SharePoint as well as think about how any changes in the structure will affect the migration of existing data. Exciting, isn’t it?
What do you think of our takeaways? What have you done to make your VLE student-centered? How does your VLE encourage innovative teaching and learning?
Below is a copy of the notes from our small ‘focus group’.
1. Looking over section one, what are the two most important features to be kept?
- Portfolio – bucket of work
2. Looking over section two, what are the three most recurring themes of the comments?
- editable/collaborative spaces for students (wikis, blogs, whatnot)
- student centered
- Portfolios – defining what it means, how it is accessible, what goes in it
- This goes beyond the current repository for all summative tasks.
- if you don’t allow common spaces, then more people will go off the reservation.
- Allow for spontaneity.
- “get out of the way”
- There is a difference between a CMS and learning environment
- Portability of work – 3.5 years average length of stay
- For teachers
- For students
- Dynamic, embedded content
- Locally hosted
- internet access
3. How can we address one or two of those recurring themes?
- Separate the tools: find the best tool to do the job well instead of relying on one tool to do things mediocre
- Define acceptable external alternatives if SP cannot do what we want/need.
- Class blog, discussion board, teacher controlled wiki, student based wiki – basic tools that need to be accessible (one example)
- personalized dashboard
- Can front page be different for different populations.
- Create shortcuts w/in the portal
- Sharing – local and global collaboration
- Interactive learning spaces
- External permissions
- Scaffolded approach to open access
- “We have to teach differently” – We need the tools/access/flexibility to teach differently
- Class activities within Moodle
- anybody create wikis
- anybody create discussion boards
- various activities
- change the views; teachers can turn elements on and off