I first experienced Cooper and Murphy at an education conference; their work on PBL is the sole reason I attended that conference. When I got home, I purchased this book.
$20 well spent.
They go through 10 steps on how to implement PBL in a classroom. My only issue is that, since they're elementary teachers who don't have multiple classrooms, I can't relate to everything. There are some teachers in my school who are in 4 or 5 different classrooms in different buildings throughout the duration of the school year. So not everything works.
What is great is that they GET that. They understand the variety of situations teachers can find themselves in. So they offer tips and tricks, alternatives, and very general ways that are easily modifiable for all types of classes/lessons/students. The book is written simplistically, but not in a way that is demeaning. Instead, it's quite clear as to what their goal is - ease any apprehension teachers may have with regards to PBL, and informing that PBL doesn't even have to be crazy!
The first three chapters/hacks describe how it may be best to set up a foundation for a PBL.
Each hack section has "Blueprints" to follow to best carry out the hack, "Overcoming Pushback" to detract naysayers, and a "Hack in Action" example.
Some of the questions/comments in "Overcoming Pushback" are ridiculous. What is worse, I'm not fully surprised by some of them.
Hack 1: Space Promoting Risk-Taking:
- How can we make fewer things teacher-selected content?
- We HAVE to allow students to struggle. We can't show a solution outright; struggle is a part of learning.
- Ask students what classroom design would best inspire and motivate them. Let THEM create posters (leave the room bare from the start) and other content that connects the math to the world.
- Discuss how elements in organizations connect to classroom learning.
- Pose a variety of questions at the start of the year to model what good questions actually are.
- Have students identify where they went wrong.
Hack 2: Teach Collaboration Skills:
- Collaboration =/= divide and conquer. It's working WITH someone else, for a PURPOSE. This includes developing a solution to a problem as a group.
- We need to preassess where students are with collaboration, curate those skills (even if it's showing a YouTube video of collaboration), and model collaboration with each other. We can even have students roleplay collaborative conversations, like with a script, including with a disagreement and good questions to gather information. Then the STUDENTS can create a class set of expecations for learning.
- Include personal reflections and action plans.
Hack 3: PBL-Worthy Content:
- high Impact Content guides PBL and helps focus on specific outcomes. It's best if these outcomes are written out as clear statements to guide learning.
- If content has high value, is needed for future studies, and has language that allows for deep understanding, then that material/standard can likely be used for a PBL unit.
- I LOVE that in the wrap-up at the end of the chapter, Cooper and Murphy articulate that while PBL units are nice for specific projects, students DO have to know how to apply that knowledge to another object/project/etc. (I had a professor who always spoke poorly about the IMP program for tat reason - students didn't know how to transfer knowledge to other situations).
Hack 4: Create a Vision:
- The authors break down the differences between PBL and traditional projects
- WE the teachers need to make OUR OWN connections between our content and the world!
- PBLs have high impact takeaways, incorporate interdisciplinary content and are based on a certain "track". Before we implement one, we need to develop questions and receive professional/critical feedback, determine one place for materials, and then launch the project (initially without directions) while allowing time for inquiry.
Hack 5: Wrap the Learning in Inquiry:
- This was one of my favorite chapters/sections. In it, Cooper and Murphy explain how to transfer high impact takeaways into umbrella questions - which students can even create when they're more familiar with the PBL process. Umbrella questions aren't leading questions that are found in textbooks, which can be answered in one or two lessons. They're contextual and very open.
- I like the "less is more" approach with questions, where multiple concepts/traditional questions are addressed in one open-ended question.
- Teachers need to prepare students for control, direction, and question development. The umbrella question should be EVERYWHERE during the duration of a PBL.
- I love the idea that a PBL is like a graphic organizer with the umbrella question at the center.
Hack 6: Shift the Ownership of Assessment:
- The Progress Assessment Tool template that is included is very helpful, as is the given example.
- We have to determine learning targets (to put in the PAT), collect exemplars of work to be done, then let students analyze them to develop group-determined strengths for each learning target. Then the teacher has to make sure those strengths are adequate before letting students move on.
- This section also provides guidance on how to help students create assessments and/or grading guidelines, as well as self- and peer-assessments.
Hack 7: Make Feedback Everyone's Business:
- This one hit close to home, since I'm constantly having to remind myself to give good feedback. We can't solely react to finished products; quality feedback occurs throughout a project so it can be immediately applied.
- I really like the idea of a poster/cheat sheet that exemplifies what quality feedback looks like for the students.
- Give feedback without grades!! This is one thing I took from the conference; it's definitely something I'll take from the book.
Hack 8: Right to a Mini-Lesson:
- Integrate direct instruction as necessary.
- The authors compare teaching to video games: give directions and information as you progress through a unit.
- There are great ideas for mini-lessons, even in a non-PBL unit. I like the different strategies offered (hands-on experiments, think alouds, video clips, non-fiction reading), provided they relate to the current content.
Hack 9: Guarantee Understanding:
- This section is a great reminder that one project grade can be broken down into grades for each learning target.
- Summative assessments are very good for individual understanding of a group project.
- Cooper and Murphy still say to place more emphasis on formative feedback...and LESS emphasis as '"grades as a weapon" to force students into learning.'
- I love the reiteration of creating units with high impact targets in mind, and not the test. The simplistic explanation makes standards-based units and assessments more understandable for me - whether or not I integrate PBL in a given unit.
- I also like how they placate those with the "overcoming pushback" section. Creating assessments ahead of time IS 100% OKAY!! It doesn't detract from learning!
Hack 10: Finsh Project in Style:
- There is great information on how to prevent an abrupt end to projects, simply because they're ending, and allow for reflection. Cooper and Murphy provide ways to create conditions for reflection.
- One good takeaway is the note that we need to plan for formal reflection, especially under the context of formative and sumamtive assessment.