Session design worked example: No. 01 - 5 schools in 1 session

Session requirements

"I want to create an RM Compare session involving 5 other schools in my Learning cluster. I want them to submit 20 items each. I want three teachers from each school to be judges. At the end of the session I need to be able to identify the host school for each item in the rank order."

System boundaries and constraints

We could use a Standard Session or a Multi-Centre Session to get this job done.

This blog post talks more about Session Design options.

Standard Session Option

A lot of the work is going to fall on me including

  • All the Items will need to be sent to me
  • I will need to QA each Item. If there are errors I will need to send them back and await their return.
  • I will need to ensure that all Items are named correctly
  • I will need to upload all Items into the system. If changes are needed I will need to make them.
  • I will need to gather all of the Judge detail and add them. If they change I will need to make the changes.
  • It is not possible for me to include meta-data to the Items
  • It will be challenging to run Advanced Reports
  • I am the single point of failure

Summary

  • It's possible but involves a lot of work and would be difficult to scale

Multi-Centre Session Option

The assumption here is that all Centres are connected (a bit of effort, but 'one and done'),

  • I create a Multi-Centre base session and share to the 5 contributing schools
  • Each schools adds their Judges and Items
    • They are responsible for Quality Assurance, including Item naming
    • They Hand-in when ready (and can 'hand-back' as many times as they like if things need changing).
  • I merge everything that is handed it and then run the merged session
  • The Judges complete their judging
  • The results includes meta-data and supports advanced reporting

Summary

  • Built for larger scale sessions, typically with more than one Licence Centre, offering more control and less work.
  • More efficient and effective

Summary

Choosing a session design in this scenario will be context specific - there is no 'right or wrong'. For example, the standard session is a bit more work for the co-coordinator but less for the contributors which may be important as people get used to the RM Compare system or lack the necessary technical skills or support to self-serve as a contributor in a Multi-Centre Session.

Using a Standard Session can look less complex but is not designed for larger scale, Multi-Centre Sessions. A lot of extra work can be created and the final results will have limited depth. For 5 schools in this scenario is it manageable but be prepared!!

Multi-Centre sessions are build for this type of thing. There is a bit of set up in getting Centres connected but this is a 'one and done' exercise. Less work, more control and deeper data than using a Standard Session. Expect to assist contributors as the familiarise themselves with the system.