Best Practices for Mid-Year Adoption

You can implement Little SIS Premium at any point in the academic cycle. It uses an intuitive interface to assist in creating linkages to current, teacher-created Classroom classes. As you add and remove students from your SIS, it updates all your classes, not only new ones.

Some schools or districts prefer to roll out Little SIS Premium as a pilot during the school year. Piloting lessens the burden of change management by starting small and working up to full adoption for the following school year. This approach gives you and your team the rest of the school year to ensure that your SIS data is complete and in the optimal format to achieve the goals that you've set forth for Google Classroom at your district.

Below are the steps to set up your first pilot job and link to current Classroom classes.

Before setting up Little SIS Premium, it is a good idea to let your pilot teachers know what changes they can expect in Classroom. Here are some of those changes:

Here's a sample email you could send teachers.

Little SIS Premium adoption contains the following steps:

  • Create a Pilot Job
  • Run Sync Analysis
  • Link to Current Classes
  • Commit Changes
  • Review Process

Create a Pilot Job

We suggest creating a pilot job as a precursor to a larger rollout. Follow the steps in the Setting up a sync job step-by-step guide to create your Pilot Job. The best practice is to create one job per school site or per pilot user group, using Inclusion and/or Exclusion Rules.

Run Sync Analysis

Once you've created your Pilot Job, must Run Sync Analysis on your job from the Scheduled Sync Jobs list to link to current Classroom classes.

RunSyncAnalysis2sm.png

Once you have run the Sync Analysis, you will move to the Sync Analysis Summary

Link to Current Classes

You must link the classes during the Sync Analysis process to push student roster changes to existing Classroom classes. To complete this process, follow the steps in the Reviewing and Approving Class Links step-by-step guide.

Commit Changes

Now that you've established links to existing Classroom classes, can sync Little SIS Premium to Google Classroom. Return to the Summary page and click Commit Staged Actions Now

reviewAndActionSummaryArrow2.png

Review Process

Once you've run the initial sync to Classroom, it's a good time to reflect on the process. You need to determine the next steps for scaling up your implementation. We recommend continuing to create Manual or Staged Jobs until you are comfortable with the process and your teachers are aware of the changes that are happening within Classroom. 

Things to consider now are:

  • Are you happy with the classes created by Little SIS Premium (i.e., the Class Name)?
    If you are happy, great! The format of your enrollment file will likely stay the same. If you do not like the class names, you may need to include more fields in your enrollment file to build a Class Name during Job creation that meets your goals.
  • Who will manage Little SIS Premium when you initialize a large-scale roll-out?
    It is important to consider who will create Little SIS Premium jobs and ensure they are staged appropriately before a large-scale rollout. Full automation eliminates the need for daily human oversight, but someone must ensure that updates to the software are implemented. If the updates impact jobs, you must make those changes to the current Job List. You also want to ensure that teachers have a method to report any incidents related to Little SIS Premium and Classroom.
Document Version Date Description of Change
1.0 3/13/2024 Remove blank link
1.1 4/18/2024 Edited for clarity, replaced commit image, verified article

 

Articles in this section

See more