Ten Things I've Learned in Going Project-BasedIt's a few days before Christmas and I expect a challenge. Students will be checked-out or hyper. However, to my surprise, they are fully engaged in a project that combines reading, writing, global awareness and critical thinking.
I've mentioned before that this year has been challenging. However, I am realizing that my students excel when I approach a subject with a project-based framework. In past years, I started with a full project-based approach. This year, I started out a little more slowly.
Here are some things I've learned over the last few years as I've transitioned toward a more project-based approach:
- Students need to be a part of the planning process. This is a pretty simple concept, but it was the hardest thing for me to realize. Student ownership needs to include students helping develop the essential questions, the scenario and the audience for projects. It took me a long time to realize that good projects begin with student inquiry.
- It's about the learning. Projects aren't crafts. They're about problem-solving. However, when I look back to my own experiences in school, I remember "projects" that were nothing more than step-by-step directions with scissors, paper and glue. This is why I include moments of structured discourse throughout the projects. I want to see them articulate what they are learning through the process as well as the product.
- Students need to learn about paradigm shifts. For many students, project-based learning goes against the style of schooling they are used to. For this reason, we talk about the following paradigm shifts: from isolation to integration, from completion to mastery, from choices to freedom, from differentiation to personalization.
- Sometimes it fails. I had a project that seemed like it would work and then two days into it, I realized that it wasn't working. It was too complex, too difficult and required resources we didn't have.
- Interdependence is critical. I used to view projects as independent activities and then I switched to totally dependence-based group projects. I now see a need for both, a sort-of middle zone that includes some independent and some group work.
- Students need varying levels of support. Some students need one-on-one conferences to go over difficult concepts. Some need tutorials or screen casts. Some need sentence stems and front-loaded vocabulary for their language acquisition issues. Still, others need help with breaking down the tasks and setting up their own deadlines. But I've learned this: sometimes it's best to just get out of the way.
- Project-based learning doesn't diminish the role of the teacher. All the talk of "guide on the side" can make it sound like a teacher is nothing more than a glorified babysitter. I've found that I am more active, building closer relationships, asking more questions in a project-based environment. It's less about managing a large group and more about working with individual students.
- The testing culture is the biggest enemy to project-based learning. I don't mind teaching to the standards, but I struggle with taking their learning from the test. The tests are shallow, isolated facts based upon recognition while the projects require critical, connected thinking.
- Assessment is vital to the process. I used to create projects with a rubric at the end. Now, I encourage student self-assessment. I ask students to be evaluative as well as descriptive. We do one-on-one conferences. It becomes less about testing and more about constant, in-the-moment, meaningful assessment.
- We don't always do projects. Sometimes I give short lectures with discussion. Sometimes we brainstorm things together as a class. Students write short blog posts and read their novels silently. Sometimes in math, we do a unit without a project.
John Spencer is a teacher, author, speaker, and incessant doodler.
He is the co-author of Wendell the World's Worst Wizard
and the co-founder of Write About .