Monday, June 28, 2010

Suskie Chap 11 pgs 167 – 179 & Chap 16 pgs 260 – 261

In Chapter 11 Linda Suskie explains the process of developing a test blue print-- “an outline of the test that lists the learning goals that students are to demonstrate on the test.”
She also gives these arguments for developing a test blue print:
•It helps ensure that the test focuses on the learning goals you think are most important (instead of just writing questions over the content without a plan for emphasis)
•It helps ensure that the test is not just asking for basic knowledge but also asks higher order thinking skills questions.
•It makes test creation faster
•It helps document student attainment of learning outcomes.
This chapter provides a recipe for creating a test blueprint and also provides an example of a test blue print on page 169.
Recipe
Step 1: List the major areas that the test will cover
Step 2: Allocate fractions of the test to each of those areas to reflect the relative importance of that area (assign points or number of questions)
Step 3: Within each area, list the learning goals that you want to assess – use action verbs
Step 4: Spread the points or test questions within the area among the learning goals within that area in proportion to their importance.

The rest of this chapter is devoted to giving nuts and bolts advice on:
•Writing Multiple Choice questions
•Avoiding Trick questions
•Writing Interpretive Exercises (an example of an interpretive exercise is one where you ask a student to read a passage and then you ask the student questions based on the reading)
•Writing Matching Items
•Writing Completion or Fill in the Blank items
These pages would be helpful for all faculty and may be a nice focus for a professional development session.

In Chapter 16 (Summarizing and Analyzing Assessment Results) pages 260 & 261, Linda Suskie advises that if a test blue print is written, it can be used to group the items with a common learning goal and aggregate the results for that particular learning goal. Some program areas a Palo Alto used this technique to assess program learning outcomes Spring 10.

No comments:

Post a Comment