Showing posts with label Gant. Show all posts
Showing posts with label Gant. Show all posts

Sunday, November 29, 2009

Presentation Days are not sacred

Students presenting and doing other meaningful things on presentation day. Students faces have been happy-faced to protect their identities.

Main Entry: pro·ject pre·sen·ta·tions
Function: noun
Definition: a culminating event during which students present their work to panels that include parents, teachers, engineers, scientists, former and current students, professors, miscellaneous experts, etc.
Eatamology: This entry will focus on a specific thing I ate out of Kevin Gant’s brain about what students can do when they are not presenting. He told me and modeled for me that students do not need to watch all the other teams’ presentations – instead there are many other more meaningful things they can do during that time. See below. I also mention an observation I ate out of Merced’s brain in 2007 that suggests that teachers maybe need to stay away from some presentations too.
Date: July 6-10, 2009 and 2007.

Now that I’m setting down to actually write out what goes into a good presentation day – I’m realizing there is a lot that goes into it. There are strategies to assemble good panels, to help better prepare your students for presentations, to prevent single team members from monopolizing a team presentation, and more. There are enough things to occupy several blog entries – so that’s what I’ll do with this topic. This entry focuses on everything but the presentations. Mainly – what should students do when it is not their team’s turn to present?

Kevin blew my mind last summer when he matter of factly said that presentation day is not sacred – there is no reason for all teams to sit quietly and watch every other team’s presentation. For most projects, sitting through all the presentations is tedious for a teacher – it’s even more tedious for a typical teenager – which creates classroom management problems. Then he modeled for me a presentation day where teams had the option to either watch other team’s presentations or do other things such as: complete the evaluation for the training session, continue preparing for their team’s presentation, continue working on their team’s project, etc. It was easy to see why this way was better. The teachers spent less time shushing restless students. The students spent more time doing things they found personally meaningful.

Now I run all my presentation days this way. Teams who are not presenting have several other things to do to keep them occupied while they wait their turn. They prepare for their presentations, finish their products, catch up on their assignments, complete collaboration evaluations, etc. Some students even opt to watch a couple presentations to help them prepare for their upcoming presentations.

I even came up with other things for me to do than watch the presentations. I actually love watching the presentations – but more and more I am opting to not be on my classes’ panels because students give much more detailed presentations when their panels consist completely of outsiders to the project. Merced made this observation years ago and I’ve observed enough to believe that he’s right. As soon as a project insider joins the panel, the students omit a lot of detail because they often assume that the entire panel has the same level of inside info as the insider. To keep the level of discussion high when I am not on panel, I give the panelists lists of good questions that are aligned to the content in the projects. I ask the panelists to use these questions to gauge the level of preparation of each presenter. See below for an example.

Related tools: Here’s a link to a set of instructions I gave to panelists who were assessing presentations for the Stuntkid project: link. Here’s a link to the scorecard I ask the panelists to complete to assess my students’ oral communication skills: link.

Wednesday, November 25, 2009

Work Suites


Main Entry: work suite
Function: noun
Definition: a section of a classroom that is set aside as a work area for a single project team
Eatamology: Last year, I finally decided to officially mark the 8 work suites in my room using parody prints of Ugly Dolls in famous paintings that I created in Notebook. Kevin Gant and Michael McDowell, two very talented and wise New Tech coaches, have often stressed the importance of displaying the group contracts in places that are easily accessible to teams. Tara Craig (co-teacher from last year) and I started hanging up their group contracts within their suites. This year, my current co-teacher Mr. Banks added his own personal touch to each work suite by hanging up PVC pipes to hold the know/need-to-know charts and team contracts for the teams that occupy each work suite.
Date: Summer 2008 (First time It sunk in my brain that group contracts must be constantly visible – I probably heard this as early as Summer 2007 but it didn’t sink until 2008) Fall 2008 (work suites adorned with ugly doll paintings and group contracts), Nov. 15 2009 (Banks installs PVC pipes to hold contracts and other team docs)

Having designated work areas for different teams is a key part of the design of my classroom that helps me to facilitate PBL teams. I do not use individual seating charts because all my students work in teams. Instead, I assign work suites to teams of 2 or 3 students that consist of 2 or 3 adjacent work stations with a team set of textbooks. Within the work suite, the students can sit wherever they like.

Each work suite has a place that holds the team contracts and know-need-to-know charts of the teams that occupy that suite. In our newest scheme, the group contracts hang above the work station that is in the center of the work suite. Since 4 teams from 4 different periods share the work suite, the group contracts are color-coded (pink = Period 1, goldenrod = Period 2, green = Period 3, blue = Period 4). When the teams start each period, they flip the pages in the work suite displays until their team contract is at the front of the display.

Having the group contract in an accessible place makes it easy for me to reference the team contract whenever I am coaching teams to refocus or to peacefully resolve conflicts. The group contracts always set nice starting points for these conversations. If they are not detailed enough to solve the problem at hand, I ask the teams to add addendums to their contracts that include strategies and new agreements to solve current team issues/conflicts.

Some of my high functioning teams reference the contract on their own when their teams hit bumpy spots and high points (during high points, my teams celebrate and these celebrations are documented in their contracts – the idea of team celebrations was eaten out of Michael McDowell’s brain). Sometimes I scaffold reflections on their contract into their work days by adding prompts in their warm-ups that reference agreements in their team contracts. Having the group contracts close at hand, makes it easy for my teams to complete these reflections.