Step 1: Development

Functions for inclusion in rubric are identified
Functions from Needs Assessment- 60% but not just them, maybe all of them.
Also include different file types and compatablility.
Support online documentation.

A rating system / design model is created
If the scores were, for example, 3,2,1, then we could filter out all of the 3s. We could see the big picture, and then just the highest scoring. It would be essential to have a multiplier, so that we could weigh our 60% or greater features from the Needs Assessment more heavily.
Explainations would have to be included in the rubric. Maybe a chart with a list of descriptors (common vocabulary)

Existing fuctionality rubric models are reviewed
Partnership members become familiar with existing rubrics.

Step 2: Implementation

Open Source Learning Management Systems to be tested are identified
Agree to eliminate as a group. Maybe drill it down to 3 for testing.

Testing environments are established
Questions about how much a self hosted vs. hosted environment would effect our functionality tests.

User Profiles to be tested are identified
test all 3 (instructor must have editing features)
Can you create custom roles within the group?

Logistics are determined
Have individuals with different roles, instead of each person doing all 3.
We need to make sure that what we are testing is worhwhile.
Set standards. IT be one role, admin be one role, etc.

Needed Materials are identified
Maybe the MTTP pilot could be imported.
Use a pilot that is already developed.